31–40 of 50 posts
Agile is ironically one of the best indicators of fixedness on the planet. It was a simple idea that has taken root, & will never ever ever be removed.
But this would leave the product manager out of a job, so I've never seen any other company even try it.
Who is this guy, and what kind of credentials does he have to sprout such drivel? It seems that like whatever sector he’s in, he has a big beef with developers. If he’s a designer like I assume from the fact it’s published in something related to UX, I suppose he wants a few months to design a whole application up front (because it’s fun!), only to then throw away 80% of it because the requirements changed halfway th…
Somehow an author with an MBA background fails to interrogate the business impact of their advice and various interpretations of agile. I’m also slightly incredulous that they got through an MBA program without the reading comprehension needed to tackle the agile manifesto… I think this is actually a blogspam article meant to drive outrage. Shame on HN for falling for it.
https://blog.pragmaticengineer.com/project-management-at-big...
I share the current disdain for "agile" workflows. In particular, I have grown very weary of every example of failure getting met with "they did agile wrong." After enough encounters with it being done in a way that does not bode well, I am forced to start questioning the general ideas. However, I do find the excessive snark against wanting to empower the developers kind of off putting. In particular, zero charity in…
The problem with this is that agile when done well is actually the best way to build software. Just because people misuse it (the name OR the method) doesn't actually make it bad. And whatever you try to replace it with, you can expect middle management to do that wrong as well.
Having a smooth and well organised release cadence is a good idea. Obviously skipping strategy and UI work is a bad idea. These tasks need to be done in parallel and inform each well thought-out sprint.
I share the current disdain for "agile" workflows. In particular, I have grown very weary of every example of failure getting met with "they did agile wrong." After enough encounters with it being done in a way that does not bode well, I am forced to start questioning the general ideas. However, I do find the excessive snark against wanting to empower the developers kind of off putting. In particular, zero charity in…
Agile is middle / project managers doing cultish makework for themselves, to codependent-ly distract from feelings of life-cycle imposter syndrome.
Coming from big corp, I definitely miss my days at smaller shops that did Agile. I feel like so much of this has little to do with the development methodology and more to do with the people though. Smart people can make any methodology. Even at big corp, more waterfall-y processes are not terrible because I think my coworkers make it alright. The author seems to be unhappy about empowered developers being problematic…
Yep. Problem developers can create larger problems with longer feedback cycles.
False. Hey, early and frequent releases, cicd, unit testing, small teams with courage and responsibility, all of those come out of agile. Yes, it come with a lot of hot air, and yes, not every project should be agile, but show some respect man.