1. http://www.testrun.co.nz/presentations.html Scrum (software development)

2. http://www.testrun.co.nz/presentations.html Scrum (software development) Why

3. http://www.testrun.co.nz/presentations.html Scrum (n): A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value. Source: “The Scrum Guide™, October 2013” Ken Schwaber, Jeff Sutherland focus on one word above…

4. http://www.testrun.co.nz/presentations.html Scrum (n): A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value. Source: “The Scrum Guide™, October 2013” Ken Schwaber, Jeff Sutherland framework people productively value products deliveringcreatively problems complex adaptive

5. http://www.testrun.co.nz/presentations.html Source: “Scrum in Church, Saving the World One Team at a Time” 2009 Arline Sutherland, Jeff Sutherland, Christine Hegarty Scrum Scrum was designed to increase productivity and improve quality through teamwork. Why

6. http://www.testrun.co.nz/presentations.html Scrum was designed to increase productivity and improve quality through teamwork. Source: “Scrum in Church, Saving the World One Team at a Time” 2009 Arline Sutherland, Jeff Sutherland, Christine Hegarty Scrum Why

7. http://www.testrun.co.nz/presentations.html Source: “Scrum in Church, Saving the World One Team at a Time” 2009 Arline Sutherland, Jeff Sutherland, Christine Hegarty Scrum Scrum was designed to increase productivity and improve quality through teamwork. Why

8. http://www.testrun.co.nz/presentations.html The History of Scrum 19301940195019601970 19801990200020102020 1939 Shewhart Cycle - Walter Shewhart 39

9. http://www.testrun.co.nz/presentations.html SpecificationProductionInspection Source: “Evolution of the PDCA Cycle” Ronald Moen, Clifford Norman 1939 Shewhart Cycle Walter Shewhart

10. http://www.testrun.co.nz/presentations.html The History of Scrum 19301940195019601970 19801990200020102020 1939 Shewhart Cycle - Walter Shewhart 39 1950 New Shewhart Cycle - Walter Shewhart

11. http://www.testrun.co.nz/presentations.html 1950 New Shewhart Cycle Walter Shewhart SpecificationProductionInspection Source: “Evolution of the PDCA Cycle” Ronald Moen, Clifford Norman Specification ProductionInspection

12. http://www.testrun.co.nz/presentations.html The History of Scrum 19301940195019601970 19801990200020102020 1939 Shewhart Cycle - Walter Shewhart 1950 Plan-Do-Check-Act - W. Edwards Deming 39 1950 New Shewhart Cycle - Walter Shewhart

13. http://www.testrun.co.nz/presentations.html Do CheckAct Plan 1950 Plan-Do-Check-Act W. Edwards Deming Source: “Evolution of the PDCA Cycle” Ronald Moen, Clifford Norman Learn & Adapt

14. http://www.testrun.co.nz/presentations.html The History of Scrum 19301940195019601970 19801990200020102020 1939 Shewhart Cycle - Walter Shewhart 1950 Plan-Do-Check-Act - W. Edwards Deming 1986 “The New New Product Development Game” Hirotaka Takeuchi, Ikujiro Nonaka 86 39 1950 New Shewhart Cycle - Walter Shewhart

15. http://www.testrun.co.nz/presentations.html 1986 The New New Product Development Game Hirotaka Takeuchi, Ikujiro Nonaka Developing products is like the sport of rugby. A holistic or rugby approach; where a team tries to go the distance as a unit, passing the ball back and forth. Moving the scrum down field {Main section of the paper} 1. Built-in instability 2. Self-Organisation 3. Overlapping development phases 4. “Multi-learning” 5. Subtle control 6. Organisational transfer of learning Source: “The New New Product Development Game” Hirotaka Takeuchi, Ikujiro Nonaka Image: “ST vs Gloucester - Match – 23” by PierreSelim - Own work. Licensed under Creative Commons Attribution-Share Alike 3.0 via Wikimedia Commons.ST vs Gloucester - Match – 23

16. http://www.testrun.co.nz/presentations.html The History of Scrum 19301940195019601970 19801990200020102020 1939 Shewhart Cycle - Walter Shewhart 1950 Plan-Do-Check-Act - W. Edwards Deming 1986 “The New New Product Development Game” Hirotaka Takeuchi, Ikujiro Nonaka 8697 39 1950 New Shewhart Cycle - Walter Shewhart 1993 Jeff Sutherland invents Scrum 93

17. http://www.testrun.co.nz/presentations.html The History of Scrum 19301940195019601970 19801990200020102020 1939 Shewhart Cycle - Walter Shewhart 1950 Plan-Do-Check-Act - W. Edwards Deming 1986 “The New New Product Development Game” Hirotaka Takeuchi, Ikujiro Nonaka 1997 “SCRUM Methodology” - Ken Schwaber 8697 39 1950 New Shewhart Cycle - Walter Shewhart 1993 Jeff Sutherland invents Scrum 93

18. http://www.testrun.co.nz/presentations.html 1997 SCRUM Methodology Ken Schwaber Source: “Scrum Development Process” Ken Schwaber Closure Planning & System Architecture Wrap ReviewAdjust Develop Sprint Learn & Adapt

19. http://www.testrun.co.nz/presentations.html The History of Scrum 19301940195019601970 19801990200020102020 1939 Shewhart Cycle - Walter Shewhart 1950 Plan-Do-Check-Act - W. Edwards Deming 1986 “The New New Product Development Game” Hirotaka Takeuchi, Ikujiro Nonaka 1997 “SCRUM Methodology” - Ken Schwaber 8697 39 1950 New Shewhart Cycle - Walter Shewhart 1993 Jeff Sutherland invents Scrum 93 1999 “Scrum Framework” ~ Jeff Sutherland 99

20. http://www.testrun.co.nz/presentations.html 1999 Scrum Framework Jeff Sutherland Source: “Scrum: A Pattern Language for Hyperproductive Software Development” Jeff Sutherland Product Product Backlog Daily Scrum 15 minutes What went well? What did not go well? Ideas to Improve process & product? Learn & Adapt 24 hours Sprint Do Act Plan Sprint 1 – 4 weeks Review Sprint Retrospective Sprint Planning Check

21. http://www.testrun.co.nz/presentations.html 1950 Plan-Do-Check-Act W. Edwards Deming Do Check Act Plan Do CheckAct Plan

22. http://www.testrun.co.nz/presentations.html The History of Scrum 19301940195019601970 19801990200020102020 1939 Shewhart Cycle - Walter Shewhart 1950 Plan-Do-Check-Act - W. Edwards Deming 1986 “The New New Product Development Game” Hirotaka Takeuchi, Ikujiro Nonaka 1997 “SCRUM Methodology” - Ken Schwaber 8697 39 1950 New Shewhart Cycle - Walter Shewhart 1993 Jeff Sutherland invents Scrum 93 1999 “SCRUM Framework” ~ Jeff Sutherland 9913 2001 “Manifesto for Agile Software Development” 01

23. http://www.testrun.co.nz/presentations.html 2001 Manifesto for Agile Software Development Individuals and interactions over processes and tools That is, while there is value in the items on the right, we value the items on the left more. Source: http://www.agilemanifesto.org/ Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan Kent Beck Mike Beedle Arie van Bennekum Alistair Cockburn Ward Cunningham Martin Fowler James Grenning Jim Highsmith Andrew Hunt Ron Jeffries Jon Kern Brian Marick Robert C. Martin Steve Mellor Ken Schwaber Jeff Sutherland Dave Thomas On February 11-13, 2001, at The Lodge at Snowbird ski resort in the Wasatch mountains of Utah, seventeen people met to talk, ski, relax, and try to find common ground and of course, to eat. What emerged was the Agile Software Development Manifesto. Representatives from Extreme Programming, SCRUM, DSDM, Adaptive Software Development, Crystal, Feature- Driven Development, Pragmatic Programming, and others sympathetic to the need for an alternative to documentation driven, heavyweight software development processes convened.

24. http://www.testrun.co.nz/presentations.html The History of Scrum 19301940195019601970 19801990200020102020 1939 Shewhart Cycle - Walter Shewhart 1950 Plan-Do-Check-Act - W. Edwards Deming 1986 “The New New Product Development Game” Hirotaka Takeuchi, Ikujiro Nonaka 1997 “SCRUM Methodology” - Ken Schwaber 8697 39 1950 New Shewhart Cycle - Walter Shewhart 1993 Jeff Sutherland invents Scrum 93 1999 “SCRUM Framework” ~ Jeff Sutherland 2013 “The Scrum Guide™” ~ Ken Schwaber & Jeff Sutherland 9913 2001 “Manifesto for Agile Software Development” 01

25. http://www.testrun.co.nz/presentations.html Sprint Planning Sprint Review Sprint Retrospective 2013 The Scrum Guide™ Ken Schwaber & Jeff Sutherland Source: 2013 “The Scrum Guide™” ~ Ken Schwaber & Jeff Sutherland The Sprint Sprint 1 – 4 Weeks Daily Scrum 15 minutes Product  What went well? What did not go well? Ideas to Improve process & product? Achievement awards? Learn & Adapt Topic 1 : What can be done this Sprint? Topic 2 – How will the chosen work get done? Product Backlog High priority Low priority 24 hours Sprint Backlog Three Questions 1.What I did yesterday? 2.What I’ll do today? 3.Any impediments? The Product Owner The Development Team Size 6 ±3 (3 to 9) The Scrum Master Definition of “Done” Definition of “Ready” Scrum Team Product Backlog Refinement Up to 10% of Sprint time Release Burndown Monitoring progress towards a Goal Sprint Burndown Monitoring Sprint progress Sprint Goal Sprint Backlog To Do WIPDone

26. http://www.testrun.co.nz/presentations.html Scrum Now 19301940195019601970 19801990200020102020 1939 Shewhart Cycle - Walter Shewhart 1950 Plan-Do-Check-Act - W. Edwards Deming 1986 “The New New Product Development Game” Hirotaka Takeuchi, Ikujiro Nonaka 1997 “SCRUM Methodology” - Ken Schwaber 8697 39 1950 New Shewhart Cycle - Walter Shewhart 1993 Jeff Sutherland invents Scrum 93 1999 “SCRUM Framework” ~ Jeff Sutherland 2013 “The Scrum Guide™” ~ Ken Schwaber & Jeff Sutherland 9913 2001 “Manifesto for Agile Software Development” 01 2014 Now

27. http://www.testrun.co.nz/presentations.html Sprint Planning Sprint Review Sprint Retrospective 2014 Scrum in 20 seconds The Sprint Sprint 1 – 4 Weeks Daily Scrum 15 minutes Product  What went well? What did not go well? Ideas to Improve process & product? Achievement awards? Learn & Adapt Topic 1 : What can be done this Sprint? Topic 2 – How will the chosen work get done? Product Backlog High priority Low priority 24 hours Sprint Backlog Definition of “Done” Definition of “Ready” Sprint Goal Source: 2013 “The Scrum Guide™” ~ Ken Schwaber & Jeff Sutherland Product Backlog Refinement Up to 10% of Sprint time The Product Owner The Development Team Size 6 ±3 (3 to 9) The Scrum Master Scrum Team

28. http://www.testrun.co.nz/presentations.html Quick Quiz Source: 2013 “The Scrum Guide™” ~ Ken Schwaber & Jeff Sutherland What are the three roles in Scrum? ☐ The Team member ☐ Project Manager ☐ Scrum Manager ☐ Product Owner ☐ The Development Team ☐ Project Owner ☐ Development Owner ☐ Tester ☐ Scrum Master

29. http://www.testrun.co.nz/presentations.html Quick Quiz Source: 2013 “The Scrum Guide™” ~ Ken Schwaber & Jeff Sutherland What are the three roles in Scrum? ☐ The Team member ☐ Project Manager ☐ Scrum Manager ☐ Product Owner ☐ The Development Team ☐ Project Owner ☐ Development Owner ☐ Tester ☐ Scrum Master ✓ ✓ ✓

30. http://www.testrun.co.nz/presentations.html Quick Quiz Source: 2013 “The Scrum Guide™” ~ Ken Schwaber & Jeff Sutherland Correctly order the following five Scrum events, ( which event happens first). Sprint Planning Sprint Review Sprint Retrospective The Sprint Daily Scrum Sprint Planning Sprint Review Sprint Retrospective The Sprint Daily Scrum

31. http://www.testrun.co.nz/presentations.html Quick Quiz Source: 2013 “The Scrum Guide™” ~ Ken Schwaber & Jeff Sutherland Product Backlog Refinement can take up what percentage of a Sprint? 10%

32. http://www.testrun.co.nz/presentations.html Source: 2013 “The Scrum Guide™” ~ Ken Schwaber & Jeff Sutherland Lets Start!

33. http://www.testrun.co.nz/presentations.html As I want so that S M L XL Acceptance Criteria ☐ Story Points Priority ID User Story XS XXL 3 6 16 40 1 100

34. http://www.testrun.co.nz/presentations.html As a scrum team member (role) I want to have a user story from the product owner (something achieved) so that I have a reminder for a conversation at a later date and also to have information in a consistent and informative format. (benefit) A user story is produced by the product owner Acceptance Criteria ☐ The user story title will be ten words or less. ☐ A user story will have the format: As a, I want so that ☐ A unique user story ID will be produced for each user story. ☐ Each user story will have a priority based on other stories. ☐ A user story will have an estimate of effort; as story points. ☐ Acceptance criteria will be produced for each user story Source: www.mountaingoatsoftware.com Mike Cohn ~ As a, I want so that. S M L XL Story Points Priority ID User Story XS XXL 3 6 16 40 1 100

35. http://www.testrun.co.nz/presentations.html Sprint Burndown Days 12345 6 7 89 10

36. http://www.testrun.co.nz/presentations.html Product Burndown for Sprint Sprint 12345 6 7 89 10

37. http://www.testrun.co.nz/presentations.html

38. http://www.testrun.co.nz/presentations.html 