|
|
|
|
|
by azangru
1937 days ago
|
|
> And yet here you are talking about processes and tools First, the Agile Manifesto is not rejecting "the items on the right". It recognizes their value. Second, the four principles of the Agile Manifesto are extremely general. It does not offer any recommendations on how to achieve the "items on the left". Scrum has a set of concrete recommendations for doing that. Third, scrum respects all the "items on the left" of the Agile Manifesto. It emphasizes the importance of "individuals and interactions", of "working software", of "customer collaboration", and of "responding to change", and offers a framework for achieving them. |
|
Second, you're focusing on the very things it says not to.
Third, you're focusing on the very things it says not to.
You can't win this, Scrum is usually a proscribed process from management forced onto teams.
That's, by very definition, is the antithesis of agile. Agile is supposed to be about self-organising teams that decide how they work best. If that's scrum, fine, but if that's imposed by management, it's not agile, it's anti-agile. SCRUM, SCRUM masters, SCRUM cards, etc., etc. etc. are all anti-agile by very definition.