Member-only story
Agile Projects Have Become Waterfall Projects With Sprints
All the agility has been sucked out of agile projects

Doing agile is not the same as being agile
Agile projects have become bloated, lazy waterfall projects with two weeks sprints. The waterfall production line approach is suited to projects with known requirements or making widgets.
Currently, agile projects are turds rolled in raisins and called roses. Any developer with half a nose can smell these are not roses and late projects or failed projects waiting to happen.
The Agile manifesto is full of enthusiasm, vibrancy and can do attitude. It empowers small teams to create software with minimal guidance and tells them to go get it.
Agile doesn’t specify exact rules to follow because you were meant to learn and improve as you went and work out the most effective way to work based on feedback. It acknowledges there are no best ways because each project is unique.
Agile promised to deliver software faster and customers to return on investment quicker. When you hype any project mythology up more than a Lady Gaga concert, disappointment is likely in 99 percent of Agile projects.