Agile Manifesto
-
-
-
-
-
-
- Value
- 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 customer's 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 maximizing the amount of work not done – is essential.
- 11. The best architectures, requirements, and designs emerge from self-organizing teams.
- 12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
- Valuable Software
- Customer
- Customer satisfaction
- Early delivery
- Continuous delivery
- It's all about priority!
- Customer competitive advantage
- Agile Processes harnessing the change
- Welcoming changing requirements
- Frequent delivery
- Working software
- From couple of weeks to couple of months
- Shorter time scale is preferred
- Business and Developers collaboration
- Job done
- Daily collaboration
- Collaboration throughout the entire project
- Even late in development
- Environment must meet the needs of developers
- Level of support must meet the needs of developers
- Recruit or develop motivated individuals
- Trust them
- Efficient and effective flow of information
- Face-to-face conversation
- Team
- Measure of progress
- Working Software
- Sustainable development
- Agile processes
- Indefinite and constant pace of sponsors, developers and users
- Agility
- Continuous attention
- Technical excellence
- Good design
- Simplicity
- Unnecessary work not done
- Necessary work done
- Best Architecture, Requirements and Design
- Self-organizing teams
- More Effective Team
- Regular tuning and adjustment of behavior
- Regular reflections
-
-
-
-
(Tools - interactions )
-
come to
(Junction - Value)
-
(Helping others - Software development)
-
(We - Software programmers)
-
(More valuable - interactions )
-
(Helping others - Junction)
-
(Value - Still valuable)
-
(Value - More valuable)
-
(More valuable - Responding to change)
-
(Still valuable - Tools)
-
(Customer collaboration - Responding to change)
-
(Comprehensive documentation - Contract negotiation)
-
(Uncovering better ways of - Software development)
-
(Still valuable - Following a plan)
-
(Comprehensive documentation - Working software)
-
(Still valuable - Comprehensive documentation)
-
and
(Tools - Processes)
-
(Following a plan - Responding to change)
-
(More valuable - Individuals)
-
(Uncovering better ways of - Helping others)
-
(Still valuable - Processes)
-
(More valuable - Working software)
-
(Tools - Comprehensive documentation)
-
(More valuable - Customer collaboration)
-
and
(Individuals - interactions )
-
(Customer collaboration - Contract negotiation)
-
(Working software - interactions )
-
(Still valuable - Contract negotiation)
-
(Software development - Junction)
-
(Following a plan - Contract negotiation)
-
(Individuals - Processes)
-
(Software programmers - Uncovering better ways of)
-
(Working software - Customer collaboration)
-
(Customer - Customer satisfaction)
-
(Valuable Software - Customer satisfaction)
-
(Early delivery - Customer satisfaction)
-
(Continuous delivery - Customer satisfaction)
-
(Early delivery - Valuable Software)
-
(Valuable Software - Continuous delivery)
-
+
(1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. - Valuable Software)
-
+
(1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. - Continuous delivery)
-
+
(1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. - Early delivery)
-
(It's all about priority! - More valuable)
-
(It's all about priority! - Still valuable)
-
(Customer competitive advantage - Customer)
-
(Agile Processes harnessing the change - Customer competitive advantage)
-
(Welcoming changing requirements - Agile Processes harnessing the change)
-
+
(2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. - Agile Processes harnessing the change)
-
+
(2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. - Welcoming changing requirements)
-
+
(Customer competitive advantage - Customer satisfaction)
-
(Working software - Frequent delivery)
-
(Working software - Customer)
-
(Frequent delivery - Customer)
-
(Shorter time scale is preferred - From couple of weeks to couple of months)
-
(From couple of weeks to couple of months - Frequent delivery)
-
+
(3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. - Frequent delivery)
-
(Business and Developers collaboration - Customer)
-
+
(4. Business people and developers must work together daily throughout the project. - Business and Developers collaboration)
-
(Daily collaboration - Business and Developers collaboration)
-
(Collaboration throughout the entire project - Business and Developers collaboration)
-
(Even late in development - Welcoming changing requirements)
-
+
(Trust them - Job done)
-
(Job done - Customer)
-
+
(Level of support must meet the needs of developers - Job done)
-
+
(Environment must meet the needs of developers - Job done)
-
+
(Recruit or develop motivated individuals - Job done)
-
+
(Trust them - Recruit or develop motivated individuals)
-
+
(Level of support must meet the needs of developers - Recruit or develop motivated individuals)
-
+
(Environment must meet the needs of developers - Recruit or develop motivated individuals)
-
+
(5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. - Recruit or develop motivated individuals)
-
(Customer - Efficient and effective flow of information)
-
(Team - Efficient and effective flow of information)
-
(Face-to-face conversation - Team)
-
+
(6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. - Efficient and effective flow of information)
-
+
(Face-to-face conversation - Efficient and effective flow of information)
-
(Face-to-face conversation - Customer)
-
+
(Working Software - Measure of progress)
-
+
(7. Working software is the primary measure of progress. - Working Software)
-
(Measure of progress - Customer)
-
(Customer - Sustainable development)
-
+
(Agile processes - Sustainable development)
-
+
(8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. - Agile processes)
-
+
(Agile processes - Indefinite and constant pace of sponsors, developers and users)
-
(Indefinite and constant pace of sponsors, developers and users - Customer)
-
(Agility - Customer)
-
(Continuous attention - Technical excellence )
-
(Continuous attention - Good design)
-
+
(9. Continuous attention to technical excellence and good design enhances agility. - Continuous attention)
-
+
(Technical excellence - Agility)
-
+
(Good design - Agility)
-
+
(Agility - Agile processes)
-
(Customer - Simplicity)
-
+
(Simplicity - Unnecessary work not done)
-
+
(Simplicity - Necessary work done)
-
+
(10. Simplicity – the art of maximizing the amount of work not done – is essential. - Simplicity)
-
(Sustainable development - Indefinite and constant pace of sponsors, developers and users)
-
(Best Architecture, Requirements and Design - Customer)
-
+
(Self-organizing teams - Best Architecture, Requirements and Design)
-
+
(11. The best architectures, requirements, and designs emerge from self-organizing teams. - Self-organizing teams)
-
+
(Regular reflections - Regular tuning and adjustment of behavior)
-
+
(Regular tuning and adjustment of behavior - More Effective Team)
-
+
(12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. - Regular reflections)
-
+
(Regular reflections - More Effective Team)
-
(More Effective Team - Customer)
-