Manifesto for Agile Software Development

Transcription

1 Rocky Mountain Information Management Association Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: 1. Individuals and interactions over processes and tools 2. Working software over comprehensive documentation 3. Customer collaboration over contract negotiation 4. Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. 1

2 Working software Responding to change Results People Individuals and interactions Customer collaboration Process Processes and tools Documentation Contract negotiation Following a plan PMI ten knowledge areas are: 1. Integration Management 2. Scope Management 3. Time Management 4. Cost Management 5. Quality Management 6. Human Resource Management 7. Communications Management 8. Risk Management 9. Procurement Management 10. Stakeholders Management 2

3 Human Resource Management Communications Management Stakeholders Management Integration Management Scope Management Time Management Cost Management Quality Management Risk Management Procurement Management The Agile movement is not anti-methodology, in fact many of us want to restore credibility to the word methodology. We want to restore a balance. We embrace modeling, but not in order to file some diagram in a dusty corporate repository. We embrace documentation, but not hundreds of pages of nevermaintained and rarely-used tomes. We plan, but recognize the limits of planning in a turbulent environment. Jim Highsmith, History: The Agile Manifesto [ 3

4 We follow these principles: 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. 1. Satisfy the customer 2. Work together 3. Motivated individuals 4. Face-to-face conversation 5. Team reflects and adjusts its behavior accordingly 4

5 1. Welcome changing requirements even late in development 2. Simplicity 3. Technical excellence and good design 4. Self-organizing teams 1. Deliver working software frequently 2. Working software primary measure 3. Maintain a constant pace indefinitely 5

6 1. Welcome changing requirements even late in development 2. Simplicity 3. Technical excellence and good design 4. Self-organizing teams 1. Satisfy the customer 2. Work together 3. Motivated individuals 4. Face-to-face conversation 5. Team reflects and adjusts its behavior accordingly 1. Deliver working software frequently 2. Working software primary measure 3. Maintain a constant pace indefinitely High results Inverted U Curve Low results Do More High results High results Low results Do More Low results Do More 6

7 Working software Responding to change Results People Individuals and interactions Customer collaboration Process Processes and tools Documentation Contract negotiation Following a plan 7