3 ms·
It’s hard to have this conversation given the countless definitions of “Agile” but I think the majority of what I’ve experienced does not help with the concerns
by Waterluvian 4y ago
It’s hard to have this conversation given the countless definitions of “Agile” but I think the majority of what I’ve experienced does not help with the concerns you raise.
Proper project management to enumerate concrete goals with well-defined timelines is what you need, which is obviously not a novel part of any Agile interpretation.
Often the desire for Agile comes from not knowing how to manage a project and reaching for the popular thing that people think will magically solve their lack of expertise.
- ClumsyPilot 4y ago> Often the desire for Agile comes from not knowing how to manage a project Corporate Agile takes thr worst of Waterfall and Agile and combines them. It frees the management from budgeting for discovery and research, which are nessesary in waterfall. They can come unprepared. Then they demand all the things they expect from waterfall - hard deadlines, no surprises. Then thry change scope on the fly because 'its agile, right'. Agile does more to excuse poor managment than it does to enable developers.
- trentnix 4y agoI think this mostly nails how Agile is largely practiced. Being prepared with a clear, concise, well-communicated vision of what you want to build is essential to developing quality software, regardless of the adopted process. Agilists frequently argued investing time and energy into crafting requirements is an “anti-pattern”, so being unprepared became the Right Way To Work TM. This is 100% dead-ass wrong.
- and0 4y ago"Agile does more to excuse poor management than it does to enable developers." ding ding ding, maybe the most succinct description I've heard