| >Ask HN: Do you think Agile/Scrum is beneficial for software delivery? Yes. >Besides being a dream for micromanagers, it seems to be more about signalling progress vs. actually making progress. It is. Management being able to change direction every 1-2 weeks is fantastic for management but can be really bad for burnout. Every day you have to talk about what you worked on and what you planned to work on like you're toddlers who can't be trusted to do work. Every two weeks you have agonizing meetings where you're expected to analyze the past weeks, and come up with plans to improve them as a team. This sounds good on paper but after years of it, you mostly want to shoot yourself. And that's assuming your team doesn't agree to a 1 week sprint, where the total meeting load can be 10% of the time spent working. And that's at companies that are pretty good at it. So yes, it's good for software delivery. But for something called agile/scrum, it's awfully process heavy, and it sucks as an engineer. |