1. Commander’s Intent To convey a big-picture view of Agile development

2. Why was change needed?

4. Project Score Card (ca 2000) Failed 23% Challenged 49% Succeeded 28%

5. Agile Central Idea “ Software development is like new product development not like manufacturing. This difference is revolutionary, and it leads to a completely new way of thinking about what software is and how to build it. ” Ken Schwaber Agile Software Development with Scrum 2001

6. Manifesto for Agile Software Development (2001) That is, while there is value in the items on the right, we value the items on the left more. Signatures to the manifesto Individuals & interactions over Processes & tools Working software over Comprehensive documentation Customer collaboration over Contract negotiation Responding to change over Following a plan

7. When I think of Agile Development

8. Self-managing, Cross-functional Teams— What are they?

9. Requirements User Stories—What are they?

10. Scrum—What is it?

11. Milestones Inch Pebbles

12. Ensuring What Gets Built Delivers Value Sometimes 16% Often 13% Features and Functions Used in a Typical System Never 45% Rarely 19% Always 7% Always or Often Used – 20% Never or Rarely Used – 64%

13. Scrum Process Flow Product Backlog Sprint Backlog 24 Hours 2–4 Weeks Daily Scrum Meeting Potentially Shippable Product Increment Sprint

14. The Scrum Cycle Planning Meeting Sprint Review Sprint Retrospective Planning Meeting Daily Scrum Daily Scrum One sprint