Comment Agile is 'fine', its not whats broken in SW DEV (Score 1) 235
I've seen "good agile" and I've seen agile twisted into a hellscape of management torture. As an organization tool, agile is 'fine' - but it doesn't solve for a broken organization. If you can't or won't manage expectations, if you can't or won't prioritize, and especially if you can't or won't do real product design, then nothing is going to solve for that. When you have management evaluations being done on checkin count or LOC metrics, then there's nothing really agile will do to save you. When your product organization gives you 30 #1 priorities and wants them all at the same time with a team of six, then you're screwed no matter what process you follow. Sure, you can always make it worse - add SAFe on top of agile for instance, and watch the gears grind to a slow gummed-up mess of cross priorities and endless quarterly 'iteration' meetings where everything has to come in at the same time and releases can't be done independently because nobody wants to put the effort into making that happen. *deep breath* Where was I? Agile... It's not the process you hate, it's how you're doing it. Software development is hard, no matter what, and agile was a process to take some of the inter-dependencies out of the mix and decouple and manage expectations by providing buy-in and shared context. If you're not doing those things *at the least*, then agile can't save you because you broke it.