People often point to the manifesto to justify aspects of Scrum or XP.
They’ll say “see right here in the manifesto it says that….”
These folks need to learn a little history.
First of all, Scrum and XP were developed in the early to mid 90s. The Agile Manifesto came out in 2001.
Second, the people involved in the creation of Scrum and XP were also involved in the creation of the Agile Manifesto.
So let’s see the timeline here
1) Scrum and XP created
2) Agile Manifesto Created
3) People use the Agile Manifesto to justify scrum or xp
Now, a few more things to note.
Since many of the same individuals were involved in the creation of both the methodology and the manifesto, OF COURSE things in the manifesto appear favorable to the methodology.
This is no different from some person having a favorite set of practices, THEN writing a “bible” that says what good practices his are, and THEN telling the world that the “bible” supports the practices!
The Manifesto was not created by the almighty.
The Manifesto was created by a few people, most of which sell payware books, methodology training and/or consulting services.
Meanwhile, much of what is in the methodology is mere slogans that appeal to the populace.
Instead of political promises like “a chicken in every pot”, the manifesto cherishes “People over process!”
But they then go out and tell you which process your people should use.
Thanks for reading.
Jordan
Pingback: How Scrumdamentalists and XP Zealots instill dysfunctional communication patterns in their students | Jordan Bortz’s Software Architecture Blog