Principles behind the Agile Manifesto
The 12 principles behind the Agile Manifesto are less known than the Manifesto but even more meaningful.
Get PDF
|
This 1-pager is part of “Skills for successful Product Owners” and “Agile & Scrum” |
The content of the PDF is roughly (without the nice graphics):
Principles behind the Agile Manifesto
- Our highest priority is to satisfy the customer through early and continuous delivery of valuable software
- Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage
- Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale
- Business people and developers must work together daily throughout the project
- Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done
- The most efficient and effective method of conveying information to and within a development team is face-to-face conversation
- Working software is the primary measure of progress
- Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely
- Continuous attention to technical excellence and good design enhances agility
- Simplicity – the art of maximizing the amount of work not done – is essential
- The best architectures, requirements, and designs emerge from self-organizing teams
- At regular intervals, the team reflects on howto become more effective, then tunes and adjusts its behavior accordingly
Nice. I think I’ll print it at the office tomorrow.
Always good to have a reminder.
Also, there is a small typo @12: adjustsits. Almost 🙂
Hi clement!
Thanks for pointing the typo out! I’ve fixed it now 🙂
Hej Clement, thanks for your feedback. Great that you liked it, please let us know how your office receives the 1-pager =)
And thanks for mentioning the typo, we will correct that (next week, most likely).