It works!
The seventh principle of the Agile Manifesto is the simplest and shortest one. Working software is the primary measure of progress. That simplicity belies a profound philosophy and modus operandi That is the outcome trumps the process.
This philosophy grates and goes against the grain of conventional wisdom. Have a problem, add process. Does that problem remain? Add more process. Unfortunately that approach tends to drain quality away and loses sight of the end goal – which in software development is working software.
Working software is the primary measure of progress.
Related articles
- Agile Principle 1 – Customer Focus (tapuniversity.com)
- Agile Principle 2 – Changing Requirements (tapuniversity.com)
- Agile Principle 3 – Deliver Work Frequently (tapuniversity.com)
- Agile Principle 4 developers and business working directly together (tapuniversity.com)
- Agile Principle 5 – Motivate, Support and Trust People (tapuniversity.com)
- Agile Principle 6 – Face to Face Interaction (tapuniversity.com)
- Good Programming Practices vs. Rugged Development (securosis.com)
- AccuRev offers glossary of agile development terms (infoworld.com)
February 11th, 2011 → 10:24 am
[...] Agile Principle 7 – Working Software (tapuniversity.com) [...]
February 12th, 2011 → 10:20 am
[...] Agile Principle 7 – Working Software (tapuniversity.com) [...]
February 13th, 2011 → 8:53 am
[...] Agile Principle 7 – Working Software (tapuniversity.com) [...]
February 21st, 2011 → 8:28 am
[...] Agile Principle 7 – Working Software (tapuniversity.com) [...]