Agile principles
Download as ODP, PDF2 likes652 views
The document outlines 12 principles of the Agile manifesto. It discusses prioritizing customer satisfaction through early delivery of valuable software. Teams should welcome changing requirements and use feedback to steer development. Working software should be delivered frequently from weeks to months to get feedback and continuously improve based on customer needs.
Agile principles
- 1. principles #1 “ Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.”
- 2. © rutherford software ltd “ We welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.” agile manifesto - principles #2
- 3. © rutherford software ltd “ Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.” agile manifesto - principles #3
- 4. © rutherford software ltd “ Business people and developers must work together daily throughout the project.” agile manifesto - principles #4
- 5. © rutherford software ltd “ Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.” agile manifesto - principles #5
- 6. © rutherford software ltd “ The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.” agile manifesto - principles #6
- 7. © rutherford software ltd “ Working software is the primary measure of progress.” agile manifesto - principles #7
- 8. © rutherford software ltd “ Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.” agile manifesto - principles #8
- 9. © rutherford software ltd “ Continuous attention to technical excellence and good design enhances agility.” agile manifesto - principles #9
- 10. © rutherford software ltd “ Simplicity — the art of maximizing the amount of work not done — is essential.” agile manifesto - principles #10
- 11. © rutherford software ltd “ The best architectures, requirements, and designs emerge from self-organizing teams.” agile manifesto - principles #11
- 12. © rutherford software ltd “ At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.” agile manifesto - principles #12
- 13. © rutherford software ltd agile manifesto - ROI satisfied customer
- 15. customer steers
- 16. prioritise value adaptability harness change
- 17. emergent design
- 18. seek feedback team game trust people
- 21. sustainable pace quality eliminate work