1. Is Agile Any Better? Damon Poole 2009 Scrum and Kanban Like Chocolate and Peanut Butter Damon Poole – CTO, AccuRev

2. Slide -2- Kanban, Lean, and Manufacturing  “Principles of Scientific Management”, Frederick Winslow Taylor, 1911  Henry Ford – Early application of “Lean” Interchangeable parts (1908) Division of labor (1908) Static assembly line (1908) Moving assembly line (1913)  Toyoda’s Automatic Loom, 1924 “Mistake Proofing”  W. Edwards Deming in Japan in 1950 Plan, do, check, act Systems thinking (“it’s the system, not the people”)  Hirotaka Takeuchi and Ikujiro Nonaka describe Scrum without calling it Scrum, 1986  Joint presentation by Schwaber and Sutherland on Scrum at OOPSLA ‘95  “Scrum was first application of Lean to software” – Jeff Sutherland

3. Slide -3- Agenda  Quick Review of Scrum and Agile Values  Common Problems  Introduction to One Piece Flow  The Simplest Thing That Could Possibly Work  Going With The Flow (aka Letting Go of Iterations)  Scaling One Piece Flow  Q&A

4. Slide -4- 14 “Critical Mass” Agile Practices Continuous Integration User Stories “As a I want Unit Tests Collocation Iteration Review Refactoring Product Owner Backlog Retrospectives ? ? Daily Standup Short Iterations $$$ $ One Piece Flow

5. Slide -5- Agile At a Glance new reviewed IssueStoryPointsEffort Remaining StateAssignment 432User wants layout pleasing to the eye2reviewed- 420User wants example templates to choose from3reviewed- 419Admin wants zero installation5reviewed- 612Manager wants dashboard view5reviewed- 599Admin wants LDAP integration5reviewed- 831Admin wants self-serve password reset2reviewed- 692User wants automatic todo list generation2reviewed- 432User wants easy task entry1reviewed- 119User wants subscription-based e-mail notification5reviewed- 332Marketing wants fancy splash screen3reviewed- 516Admin wants 1-click license update2reviewed- 533User wants app to be ready in 3 seconds or less5reviewed- 619User wants app to work using Chrome5reviewed-

6. Slide -6- Agile At a Glance new reviewed todo $$$ $ Backlog (APM)

7. Slide -7- Agile At a Glance new reviewed todo wip coded tested done Backlog (APM) Iteration Burnup 10/2 10/4 10/9 10/11 10/1510/1710/1910/2310/25 10 20 30 40 0 Story Points

8. Slide -8- Agile At a Glance new reviewed todo wip coded tested done prod 9612 as a user I want… 6921 as a user I want… 6291 as a dba I want… 2196 as an admin I… 1962 as an admin I… 1296 as a casual user I… 1269 as a dba I want… Iteration Review Retrospective Backlog (APM)

9. Slide -9- Agenda  Quick Review of Scrum and Agile Values  Common Problems  One Piece Flow, the Scrum/Kanban overlap  The Simplest Thing That Could Possibly Work  Going With The Flow (aka Letting Go of Iterations)  Scaling One Piece Flow  Q&A

10. Slide -10- Common Agile Problems  Testers want to test completed stories, but need stable builds with those stories to do so.  Codebase is most stable at end of iteration, hard to get and stay stable during the iteration  Identifying which change or changes broke a build  Maintaining a build which only contains done stories  Keeping story status and the codebase in sync

11. Slide -11- Mini-Waterfall 1 2 3 4 1 2 3 4 5 6 7 8 5 6 7 8 9 10 11 12 9 10 11 12 1 2 3 4 1 2 3 4 5 6 7 8 5 6 7 8 9 10 11 12 9 10 11 12

12. Slide -12- Dev and QA Offset by an Iteration 1 2 3 4 1 2 3 4 5 6 7 8 5 6 7 8 9 10 11 12

13. Slide -13- Agenda  Quick Review of Scrum and Agile Values  Common Problems  One Piece Flow, The Scrum/Kanban overlap  The Simplest Thing That Could Possibly Work  Going With The Flow (aka Letting Go of Iterations)  Scaling One Piece Flow  Q&A

14. Slide -14- Traditional Development is Like The Game of Telephone CustomersProduct Manager ArchitectDevelopersTest & Doc Customers 7 mos. SpecifyDesignCode Integrate Write tests Test Doc

15. Slide -15- Agile Leverages People’s Memory and Conversations Design Code Integrate Write tests Test Doc Specify CustomersTeam Customers 1 month days Developer Test & Doc

16. Slide -16- Iteration After Iteration SpecifyDesign Code Integrate Write tests Test Doc WIP limit of 3 stories

17. Slide -17- Continuous Integration SpecifyDesign Code Integrate Write tests Test Crunch Time Doc Big Bang

18. Slide -18- Agenda  Quick Review of Scrum and Agile Values  Common Problems  One Piece Flow, The Scrum/Kanban overlap  The Simplest Thing That Could Possibly Work  Going With The Flow (aka Letting Go of Iterations)  Scaling One Piece Flow  Q&A

19. Slide -19- $5M per lane $11M per lane

20. Slide -20- “Complete” Feature Sets $ $ Architecture Highest Value Full Featured Future Proof “Complete” Traditional Development Agile Development $ $ $ $ $ $ $ $ $ $ $ $ $ $ Done as a unit Ready at the end Feedback at the end Some features every iteration Feedback every iteration Re-plan after every iteration A A A A A A A A A A A A A A A A A A $ $ $ $ $ $ $ $ $ $

21. Slide -21- Major Release Contents

22. Slide -22- Working With Dependencies

23. Slide -23- person days Advanced Dependency Reduction 12 28

24. Slide -24- Agenda  Quick Review of Scrum and Agile Values  Common Problems  One Piece Flow, The Scrum/Kanban overlap  The Simplest Thing That Could Possibly Work  Going With The Flow (aka Letting Go of Iterations)  Scaling One Piece Flow  Q&A

25. Slide -25- Decoupling Done Iteration review Retrospective Backlog grooming Story point estimation Iteration planning

26. Slide -26- Decoupling Done Iteration review Retrospective Backlog grooming Story point estimation Iteration planning

27. Slide -27- Decoupling Done Iteration review Retrospective Backlog grooming Story point estimation Iteration planning

28. Slide -28- Decoupling Done Iteration review Retrospective Backlog grooming Story point estimation Iteration planning

29. Slide -29- Iteration Gaps 1 1 2 2 3 3 4 4 1 1 2 2 1 1 2 2 3 3 4 4 1 1 2 2 3 3 4 4 1 1 2 2 3 3 4 4 1 1 2 2

30. Slide -30- Iteration Gaps 1 1 2 2 3 3 4 4 1 1 2 2 1 1 2 2 3 3 4 4 1 1 2 2 3 3 4 4 1 1 2 2 3 3 4 4 1 1 2 2

31. Slide -31- Continuous Flow Based on Work Schedule limit or story point limit WIP limit of 3 stories or X story points done

32. Slide -32- Agenda  Quick Review of Scrum and Agile Values  Common Problems  One Piece Flow, The Scrum/Kanban overlap  The Simplest Thing That Could Possibly Work  Going With The Flow (aka Letting Go of Iterations)  Scaling One Piece Flow  Q&A

33. Slide -33- main ws Continuous Integration on Mainline Only MinutesHours Lots of small changes in the form of user stories. CI

34. Slide -34- A B ws Multiple Stages of Continuous Integration MinutesHours CI int CI Daily

35. Slide -35- A B ws Multiple Stages of Continuous Integration MinutesHours CI int CI Daily staging CI done

36. Slide -36- Conclusion  Many Lean and Kanban concepts and practices can be applied to Scrum Decoupling Lean thinking One piece flow WIP limits Eliminating waste

37. Slide -37- Resources/Q&A  Damon Poole (dpoole@accurev.com)dpoole@accurev.com  http://www.accurev.com/agile-resource-center.html http://www.accurev.com/agile-resource-center.html  Free 188pg book, Do It Yourself Agile http://damonpoole.blogspot.com http://damonpoole.blogspot.com  Continuous Integration, Paul M. Duvall  The Toyota Way – Jeffrey Liker  Extreme Programming Explained - 2nd Edition, Kent Beck  Agile Software Development with Scrum, Ken Schwaber & Mike Beedle  Lean Software Development, Mary Poppendieck and Tom Poppendieck