4 ms·
It seems the opposite to me. There's nothing stopping you from continually improving processes under the async model. On the other hand, Scrum retrospectives a
by kethinov 12y ago
It seems the opposite to me. There's nothing stopping you from continually improving processes under the async model.
On the other hand, Scrum retrospectives are token at best because they assume the premises of Scrum. You can't adopt any reforms unless those reforms fit into the narrowly-tailored practices of Scrum.
As such, any reforms that involve replacing the daily standup meeting, the sprint planning meeting, or changing anything about how Scrum works at all are not open to discussion. How is that "Agile?"
- icambron 12y ago> You can't adopt any reforms unless those reforms fit into the narrowly-tailored practices of Scrum. I don't think Scrum is nearly that dogmatic in its posture or that inflexible in its prescriptions, but even if I'm wrong, maybe you should consider adopting Scrum-but-without-the-rigidity-you-think-it-has. Of course you can do as you please; you don't need a new capitalized term to make that true.
- kethinov 12y agoAnecdotally, whenever I try to suggest Scrum-but-without-the-rigidity, I just get dogmatic "that's not Scrum" responses.
- dragonwriter 12y ago> As such, any reforms that involve replacing the daily standup meeting, the sprint planning meeting, or changing anything about how Scrum works at all are not open to discussion. How is that "Agile?" Its not. Scrum is a collection of practices (many of which may have been developed through an Agile-like attitude wherever they originated) dictated, adopted, packaged, and sold as exactly the kind of processes-over-people-and-interactions manner against which the Agile Manifesto is a reaction. Almost all of the individual practices of Scrum are good ideas to consider (whether or not they should be applied is organization-specific) in Agile/Lean organizations, but Scrum, qua Scrum, is not Agile.