This document provides an overview of agile methodology compared to traditional waterfall methodology. It discusses that agile is more suitable for new product development where requirements are evolving, while waterfall is better for maintaining mature systems. Agile focuses on quick iterations, customer involvement, and frequent releases to adapt to changes. Though agile has less formal processes than waterfall, it still includes change control and quality assurance. The roles and responsibilities in agile include business analysts to define requirements, architects to design solutions, developers to build code, testers to validate quality, and project managers to deliver projects on schedule and budget.

1. Agile MethodologyDavid Mann, CIO July 8, 2010

2. People are more important than any process!2

3. The most important thing about process is "To Have One" Examples of SDLC processes:

4. Agile (MSF for Agile, SCRUM, LEAN, …)

5. Waterfall

6. Spiral

7. Extreme Programming

8. ASD

9. Rational Unified3

10. PMI PMBOK (PMP)CMM19691991MSF 4.02006MSFCMM19941991ScrumDSDMExtreme ProgrammingFeature Driven (FDD)Adaptive (ASD)LeanCrystal ClearMSF 4.0 for Agile19931995199920002000200320052006Rational Unified Process1981MSF 4.0 for CMM2006Some processes are more AdaptiveSome processes are more PredictiveAdaptive/Predictive ScaleADAPTIVEPREDICTIVEAGILEITERATIVEWATERFALL

11. Which one is right for me?Agile is more suitable for new product development where the scope gradually emerges and continues to evolve. It is appropriate for new business model in a changing marketplace

12. Waterfall is more suitable for static models with defined unchangeable scope. It is appropriate for maintaining mature systems with mature business model5

13. Agile MisconceptionAgile is not about rushing things; but if Agile is applied things gets delivered faster with higher quality. Why?

14. Short Sprints (iterations) - 2 to 3 weeks

15. Full Customers Involvement to adjust course

16. Frequent Releases & Check-Points

17. Multi tracks

18. Focusing on delivering software (not process)