3 ms·
Working with agile for the last half-year. while it does make people agile, i.e. stir things up with daily stand-ups etc, it also causes more chaos on the tech
by ausjke 8y ago
Working with agile for the last half-year.
while it does make people agile, i.e. stir things up with daily stand-ups etc, it also causes more chaos on the technical side.
anyone can pick up any stories, after a while there is nobody that is an expert in any domain, everyone knows a little about everything but nobody knows any subject deeper, no more domain expert. Now bugs took forever to debug, the whole group is constantly in panic mode and burnt out.
to make things worse, document is neglected due to agile's own philosophy and due to the daily chaos, and it makes development much much slower.
In short, agile gets everyone going and looking busy, but the product can never deliver because nobody knows enough to fix hard issues. Many of them are senior developers, the old model seems working better, a bit slower and quieter but products are out of the door with good quality.
Agile is bad from my experience so far, our product is embedded system that can't really be sprinted like those fancy front-end UI projects and such. Agile does not fit us well.
- cromulent 8y agoAgile isn't standups, nor user stories, nor sprints. They have been attached to it, but you can be agile without any of those things. My understanding of the "Working software over comprehensive documentation" is based on all the stupid documents that no-one ever read. You should still document the software for your colleagues, not for imaginary ISO9001 auditors. There are so many charlatans in this area, it is frightening.