Question 3
a
Agile Processes
• Are based on three key assumptions
1. It is difficult to predict in advance which requirements or customer priorities will change and which will not.
2. For many types of software design and construction activities are interleaved (construction is used to prove the design)
3. Analysis, design, and testing are not as predictable from a planning perspective as one might like them to be
• Agile processes must be adapt incrementally to manage unpredictability
• Incremental adaptation requires customer feedback based on evaluation of delivered software increments (executable prototypes) over short time periods
b
Agility Principles
1. Highest priority is to satisfy customer through early and continuous delivery of valuable software
2. Welcome changing requirements even late in development, accommodating change is viewed as increasing the customer’s competitive advantage
3. Delivering working software frequently with a preference for shorter delivery schedules (e.g. every 2 or 3 weeks)
4. Business people and developers must work together daily during the project
5. Build projects around motivated individuals, given them the environment and support they need, trust them to get the job done
6. Face-to-face communication is the most effective method of conveying information within the development team
7. Working software is the primary measure of progress
8. Agile processes support sustainable development, developers and customers should be able to continue development indefinitely
9. Continuous attention to technical excellence and good design enhances agility
10. Simplicity (defined as maximizing the work not done) is essential
11. The best architectures, requirements, and design emerge from self-organizing teams
12. At regular intervals teams reflects how to become more effective and adjusts its behaviour accordingly
