Wrong definition of Agile. Narrate your experiences.
- Agile is all about having stand-ups.
- Agile is all about having JIRA updates, burn down reports, velocity, story points, release cadence & similar jargons.
- Agile is all about having meetings, sprint planning, sprint review, retrospectives, story time, etc.
- Agile is all about making the code work just to show the output at the demo.
- Agile helps in continuous improvement of something. (Nobody knows what’s that ‘something’)
With no offense to people in agile role, I want to ask everyone: Is agile all about understanding its definition in a wrong sense? What’s your story like? Comment.
CTO: "Points are for complexity, we'll use a fibonacci system for increasing order of complexities"
Engineers: "Ok, that makes sense"
3 months later
"Product" Manager: So it seems we have done 100 points last sprint, let's ~~plan~~ groom the next one for 90-110 points in the next 2-3 hours
Engineers: 💀
I have immense respect for SM or agile coach but One of core problem of Agile coaches or SM is lack of understanding the core principles, the very first principles of AGILE that ,” This is and must be used an feedback loop to improve upon as Team “ rather then this many people just concentrate on Metrics and Agile day to day calls etc . Even the management of many companies think it as tool/process to get reports about performance, while it’s NOT! . You ask people where did the Agile originate from? When the first founder thought about this ,what was the original idea ? And where are we taking it ? ..sadly we made it as much complex as we CAN! Like they took advice “Take one idea , think day and night about it , make it your passion so that the desired output is as much complex as possible .
Glad to see you bringing so many unanswered questions.
And your last sentence not only answers every question, but also raises an existential question about a few people that are in some so-called Agile roles.