Naives are spoiling the party but they play a crucial role in making Agile successful. Coaches are stuck in the process and true Agilist would know Agile is an outcome process flaws, yep, the process flaws urged to find a way to focus on outcome with the meaningful process.

Unfortunately within Agile the narrowed vision and poor execution let the teams camouflage waterfall into Agile

While there is plenty to improve one such is story pointing.. I even wouldn’t encourage you to use the word estimation along with the word story point because the problem starts from there. Teams are often forgetting Agile prioritize responsibility and commitment then ordering/dictating. Estimation is enforcement to stick to the timeline. As I mentioned in the beginning Agile advocates the outcome and not the process.

I recently stumbled on a conversation with some of the folks debating is it okay to story point a story to .5hrs and the so-called experienced guy said that’s not allowed as we need to follow Fibonacci numbers only.

I really don’t understand why Fibonacci numbers are having such a controlling effect. If someone knows Agile suggests identifying the complexity of to ballpark MVP release plan. Please note it’s “ballpark” MVP plan. If you are having a world shuttering delivery then Agile can’t help. The project team should be allowed to deliver the feature in the next sprint if a feature is stuck in the given sprint due to any reason that’s including valid and invalid. Crushing to achieve somehow would definitely reflect in the future release either directly or indirectly. Many fail to read the indirect impact and think the crushing works 🙁

When you have energized a responsible team Agile is bliss and the outcome would be world-class.