Unfortunately all good things must come to an end and regrettably my blog is no different! Sadly, this will be my last and final blog on all things Agile. However I do intend to go out with a bang and what better way to do that then to talk about the infamous “Manifesto for Agile Development”.
I think I may have mentioned it in some form or another way back in my very first blog (yes I know – seems a lifetime ago now!) but today I shall go into it in much more detail as I firmly believe that it is the final step in discovering and learning about ASD.
In the year 2001 – between the 11th and 14th of February to be precise, many of us were making final preparations for our Valentines Day surprise but seventeen men were meeting the Wasatch Mountains in Utah to ski, relax and find common ground. What emerged after this weekend was Agile Software Development Manifesto. Experts from all the different areas of software development were in attendance, including some from XP (extreme programming) and Scrum. They all wanted the same thing – an alternative to their current document heavy system development. They called themselves “The Agile Alliance”.
It is important to emphasize that the Agile movement is not anti-methodology. It was all about restoring balance and embrace modelling, but it just wanted rid of the dusty cupboards of documentation. The Alliance claimed that they embrace documentation but just not hundreds of pages of never-maintained and rarely-used tonnes.
There are 12 principals to the agile manifesto and these 12 principals should always be adhered to.
1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
2. Welcome changing requirements, even late in development. Agile processes harness change for the customers competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
4. Business people and developers must work together daily throughout the project.
5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors, developers and users should be able to maintain a constant pace indefinitely.
9. Continuous attention to technical excellence and good design enhances agility.
10. Simplicity – the art of maximising the amount of work done, is essential.
11. The best architectures, requirements and design emerge from self-organising teams.
12. At regular intervals, the team reflects on how to become more effective and then tunes and adjusts it’s behaviour accordingly. So there we have it, the 12 principals of Agile Software Development, thought of by the 17 members of the Alliance – Kent Beck, Mike Beedle, Arie van Bennekum, Alistair Cockburn, Ward Cunnignham, Martin Fowler, James Grenning, Jim Highsmith, Andrew Hunt, Ron Jeffries, Jon Kern, Brian Marick, Robert C Martin, Steve Mellor, Ken Schwaber, Jeff Sutherland and Dave Thomas.
Theres not much left for me to say except thank you for reading, liking and commenting my blogs these past few weeks. Who knows what the future holds, I might be back with a new blog sometime soon. Whatever happens though just remember – WE LOVE AGILE SOFTWARE DEVELOPMENT!!