3 ms·
So true. But then, Agile solved problems developers had, not project managers, sales people, or accountants. In fact, it caused those people more problems. It
by marcus_holmes 8y ago
So true. But then, Agile solved problems developers had, not project managers, sales people, or accountants. In fact, it caused those people more problems.
It was only ever going to be actually implemented in developer-run organisations, because only then are developer problems more important than everyone else's problems.
Maybe that's the answer - more developer-run organisations.
- hippich 8y agoAnd finding developer-run customers. I wonder how many such customers exist.
- wirrbel 8y agoI think agile is usually presented as an approach that tries to reduce a split between the business and the developers. If you take the business out of the equation you usually get development models that just-for-fun open source projects have. Waterfall is cool with customers and sales, at least it was if it wasn't risky. So agile is a risk minimation strategy.
- geezerjay 8y ago> Maybe that's the answer - more developer-run organisations. I don't agree. Once you put a developer in a project management role, he starts to experience problems associated with managing projects and using solutions to those problems. When that happens, the developer ceases to be a developer and becomes quite plainly a project manager.
- lostcolony 8y agoThe whole idea of a sprint commitment, of pointing, of measuring velocity, of a sprint demo, is in deference to the business need to plan and adjust priorities. It does them based on realities, whereas older more waterfall style methods tend to due them on hypotheticals, decisions made with the least amount of information, and then the business wonders why the heck everything is late.
- octorian 8y agoI was once on a project where the managers loved it, because it gave them the ability to micro-manage a project like never before. They got daily status meetings, and bi-weekly cycles to adjust things.