>> It is one of the ways of putting the manifesto into practice. > It is not because it specifically mandates a given methodology imposed upon a team. You are

>> It is one of the ways of putting the manifesto into practice. > It is not because it specifically mandates a given methodology imposed upon a team. You are misreading what I have written. Yes, Scrum specifically mandates a certain set of practices. However, all these prescribed practices are aligned with the agile manifesto. The manifesto never said be anarchic. The manifesto never said do not follow any processes in your work. If that were your understanding of the manifesto, you would have to object to all and any processes that have any predefined structure to them. Code reviews? Nope, that's a process. Pair programming? Nope, that's a process. TDD? Nope, too rigid. And so on. Scrum is A way to put agile values and principles into practice, not THE way. But it is certainly not antagonistic to the manifesto. > And Scrum might be a good place to start with in theory, while in practice, it's become in many corporations as the standard way of operations. I am re-reading this sentence, and the previous two paragraphs, and just can't connect them together into a coherent thesis. Scrum is a good place to start in theory? — Well, yeah; that's what I've been saying here. — But in many places Scrum is practiced atrociously? — Well, yeah, don't do it atrociously then; do it properly.