I like these weekly roundups as I often miss stuff. One article in the last that caught my eye was about the 20th anniversary of the Agile Manifesto. This is now almost a religious text and, similar to other holy books, hasn’t changed significantly since publication. One of my family recently received holy ordination (Scrum Master training) and has the zeal of the newly converted. Me, I like the focus on user stories as a way of linking value to development tasks…:
[…] While there were differences of opinion on the specific merits of one method over another, the attendees agreed that their shared values and beliefs dwarfed these differences. The result was a Manifesto for Agile Software Development which outlined 12 principles to delivering software, based on four key values:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
As these principles and processes gained global recognition, enterprises began to understand that there was a better way of “doing” software delivery and, over the past 20 years, it’s been remarkable to watch an idea that stemmed from a three-day retreat shape the way the world approaches development and ultimately become a massive movement.
Interestingly enough, not one word has been changed in the Manifesto since its creation. But given all the advancements in the last 20 years, is it still relevant? Or should it be treated like a historical document that has long since served its purpose?