Re: Agile isn't nebulous
But that's the OPs point. "Agile" development with the deadlines defined at the start isn't Agile. Agile requires the whole business to adapt to incremental deliveries. That's what makes it so difficult to do properly.
My current project is supposedly Agile yet every quarter all the teams plan what they be working on for the next 3 months. That's not Agile. Nevertheless the Agile process (refinement, review, retro) is proving useful in driving out requirements, and while we've still not connected to the back end the customer has the first 4 pages of the journey. We've prioritised what we can deliver and the customer now has the value of being able to see the stupid design decisions they've made on screen rather than have us explain what's wrong with them.
You can rail against Agile all you like, it won't remove the requirement for you to understand the process for your next job. Learn it so you can use it to help deliver software better. Unless you genuinely believe the best way to deliver software is to spend 3 months thinking then a year building exactly what you thought about.
Biting the hand that feeds IT
