5 ms·
There is unfortunately a large gulf between “agile” and “Agile” development these days. The former refers to development generally in line with the agile manif
by kd5bjo 7y ago
There is unfortunately a large gulf between “agile” and “Agile” development these days. The former refers to development generally in line with the agile manifesto, with processes tailored to the needs of the team and the project. The latter is a buzzword used by consultants to convince management to put their favored bureaucratic method in place, usually some variant on the scrum system.
- bamboozled 7y agoThis is mostly what I see happen too, "Agile" is used an excuse to introduce some type of bureaucratic process to fix what is actually pathological cultural / leadership issues.
- NicoJuicy 7y agoI would have upvoted this 3 times, if I could
- logicchains 7y agos/fix/try and fail to fix.
- bamboozled 7y agoYup, thanks for that, this is what I meant.
- hinkley 7y agoAgile as practiced by nontechnical managers is essentially a hill climbing algorithm. And I think we all learned in college that hill climbing rarely if ever finds the optimal solution. Often it doesn’t even find Good Enough. But it’s the best thing you can see in the vicinity so it gets labeled Good Enough even over the protests of people who have done it better elsewhere.
- krinchan 7y agoThis. Our team tends to take more of a Kanban approach and we've yet to miss a quarterly delivery and always have a good sense of how far along we are. Meanwhile, the higher ups think it's black magic we don't spend 4 hours in "sprint planning" every two weeks.
- tech_tuna 7y agoKoolaid.