The Agile Manifesto (www.agilemanifesto.org) is the rally cry of all software developers against the bureaucratic and wasteful, document-heavy and plan-driven traditional methods of building software. However, it is almost 10 years old now. While it has revolutionized the way we deliver solutions to our customers, it is somewhat outdated.
Scott Ambler and I suggest a few minor changes and additions to reflect the modern realities of agile projects in the enterprise.
Take a look here, where Scott has published an updated version of the Agile Manifesto and its supporting principles. We welcome your feedback!
I've recently been working with Mark Lines of UPMentors and we've had some interesting discussions around evolving the Agile Manifesto which I thought I would share here to obtain feedback. Note that this is not any sort of official position of IBM, nothing in my blog is by the way (unless explicitly stated so), nor is it some sort of devious plot to take over the agile world (although if we did have some sort of devious plot, we'd make the exact same claim). What we hope to accomplish is to put some ideas out there in the hopes of getting an interesting conversation going.