Agile was originally a [software] development philosophy/methodology which included planning and delivery by the entire development team together. Early on it was adopted by consulting shops for good reasons. Today it seems Agile is used as a [software] development delivery mechanism with planning being externalized. If the folks writing the instructions to tell the computer what to do aren't in the room when discussing the end goal/outcome then you're just setting up a feature factory. I suppose some folks just want a "responsive" feature factory...
Read the article. The authors suggestions won't work because why wouldn't teams have done that in the first place? Agile as we know it is just productionized micromanagement.
I think the solution to this is for individual development teams to discuss with each other what works best for them instead of being told to "do Agile", attend tens of meetings each sprint, and enter stuff into Jira constantly. But that is in direct conflict with the needs of the business as stated in the article: scheduled software delivery.
4 comments
[ 3.7 ms ] story [ 19.4 ms ] threadI think the solution to this is for individual development teams to discuss with each other what works best for them instead of being told to "do Agile", attend tens of meetings each sprint, and enter stuff into Jira constantly. But that is in direct conflict with the needs of the business as stated in the article: scheduled software delivery.