Yeah, unfortunately I did and have been declined several times to experiment. I've also suggested Kanban too since it feels more in line with the pace and the lacking requirements and also shut down several times.
I like focusing on the root motivation. I haven't been able to get to it based on previous conversations. It seems to be perceived velocity because of the increased visibility from what I've gathered but the fact that we don't even have the option to experiment leads to a bigger issue IMO. The teams just aren't empowered to adjust course.
Saying this probably indicates more problems but they also insist on demos each week and demos/retros every 2 weeks. Also they want metrics/retros to track team velocity.
How much time per week do you have dedicated to sprint meetings? Another issue we have is requirements are always lacking because it’s always fires (and everything is P1).
They are also forcing time based pointing onto the teams too. 1 point per engineer day. There are other issues with the leadership expecting each engineer to be able to support 5-6 “points” a week but that’s another story.
Exactly that being a problem within itself. It feels so counter to the philosophy of Agile being “people over process”. If the people are saying they need more prep time why aren’t they listening?