This document provides an overview of agile software development. It begins by outlining the principles of the Manifesto for Agile Development, which values individuals, interactions, working software, and customer collaboration over processes, tools, documentation, and contract negotiation. The document then contrasts the traditional waterfall model with the iterative agile model. It notes several problems with waterfall such as difficulty adapting to change and long waits for value. Benefits of the agile model are then outlined, including increased productivity, reduced risk, higher customer satisfaction, and improved code quality. Case studies from a survey and Yahoo highlight positive results from adopting agile such as increased productivity and team morale.

1. Agile Software
Development
An Overview

2. “Simplicity does not precede
complexity, but follows it.”
-Alan Perlis
American computer scientist,
inventor of Algol (the mother of object oriented languages)

3. Manifesto for Agile Development

4. Manifesto for Agile Development
Individuals and interactions over processes and tools

5. Manifesto for Agile Development
Individuals and interactions over processes and tools
Working software over comprehensive documentation

6. Manifesto for Agile Development
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation

7. Manifesto for Agile Development
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

8. How does it work?

9. Iteration

10. Iteration

11. Iteration

12. Waterfall
Release
Plan & Test
Design Code
Analyse
6-12 months
= potential release

13. Plan
Iteration
Iteration
Iteration
Iteration
Iteration
Test
Code
Iteration
Design
Analyse
1-3 weeks
Iteration
Iteration
Iteration
Agile Iterations
Iteration
Iteration
Release
= potential release

14. Problems with Waterfall

15. Problems with Waterfall
Difficult to react to change

16. Problems with Waterfall
Difficult to react to change
Stakeholders must wait to
see tangible business value

17. Problems with Waterfall
Difficult to react to change
Stakeholders must wait to
see tangible business value
Web applications appear static
potentially losing customers

18. Problems with Waterfall
Difficult to react to change
Stakeholders must wait to
see tangible business value
Web applications appear static
potentially losing customers
Stressful crunch periods
towards end of project

19. Problems with Waterfall
Difficult to react to change
Stakeholders must wait to
see tangible business value
Web applications appear static
potentially losing customers
Stressful crunch periods
towards end of project
Increased cost

20. Benefits of Agile

21. Benefits of Agile
Increased Productivity

22. Benefits of Agile
Increased Productivity
Reduced Risk

23. Benefits of Agile
Increased Productivity
Reduced Risk
Higher Customer Satisfaction

24. Benefits of Agile
Increased Productivity
Reduced Risk
Higher Customer Satisfaction
Customer Feedback Loop

25. Benefits of Agile
Increased Productivity
Reduced Risk
Higher Customer Satisfaction
Customer Feedback Loop
Visibility & Accountability

26. Benefits of Agile
Increased Productivity
Reduced Risk
Higher Customer Satisfaction
Customer Feedback Loop
Visibility & Accountability
Increased Code Quality

27. Benefits of Agile
Increased Productivity
Reduced Risk
Higher Customer Satisfaction
Customer Feedback Loop
Visibility & Accountability
Increased Code Quality
Easier, Accurate Estimation

28. Benefits of Agile
Increased Productivity
Reduced Risk
Higher Customer Satisfaction
Customer Feedback Loop
Visibility & Accountability
Increased Code Quality
Easier, Accurate Estimation
Creates a Culture of Success

29. Watson my
good man,
Agile
would I would
sounds
overlook
spiffing
something as
Holmes, but
elementary as
what about the
the facts?
evidence?

30. Dr. Dobb’s Journal Survey
642 developers and managers surveyed after adoption of Agile...
Factor Improved No Change Worsened
Productivity 82% 13% 5%
Quality 77% 14% 9%
Stakeholder
78% 15% 7%
Satisfaction
Cost 37% 40% 23%
http://www.ddj.com/architect/207600615?pgno=1 May 07, 2008

31. Yahoo!: A Case Study
“At Yahoo!, we have migrated nearly 90 projects to Scrum
in the last 30 months, totalling almost 900 people.”
-Pete Deemer,
Chief Product Developer, Yahoo!

32. Yahoo! A Case Study
Productivity
68% of respondents reported Scrum is better or much better;
5% reported Scrum is worse or much worse;
27% reported Scrum is about the same.
Team Morale
52% of respondents reported Scrum is better or much better;
9% reported Scrum is worse or much worse;
39% reported Scrum is about the same or much worse.

33. Yahoo! A Case Study
Adaptability
63% of respondents reported Scrum is better or much better;
4% reported Scrum is worse or much worse;
33% reported Scrum is about the same.
Accountability
62% of respondents reported Scrum is better or much better;
6% reported Scrum is worse or much worse;
32% reported Scrum is about the same.

34. Yahoo! A Case Study
Collaboration and Cooperation
81% of respondents reported Scrum is better or much better;
1% reported Scrum is worse or much worse;
18% reported Scrum about the same.

35. Yahoo! A Case Study
According to Product Owners, Team productivity
increased an average of 36%.
85% of team-members stated that they would continue
using Scrum if the decision were solely up to them.

36. For your consideration.

37. Questions & Discussion