testrun co nz testrunnz Scrum software development testrun

testrun. co. nz @testrunnz Scrum (software development)

testrun. co. nz @testrunnz Scrum Why (software development)

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

testrun. co. nz @testrunnz Scrum (n): A framework within whichpeople can productively complexadaptive address complexproblems adaptive problems, while products productively creatively delivering creativelyand delivering productsvalue of the highest possible value. Source: “The Scrum Guide™, October 2013” Ken Schwaber, Jeff Sutherland

testrun. co. nz @testrunnz Why 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

testrun. co. nz @testrunnz Why 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

testrun. co. nz @testrunnz Why 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

testrun. co. nz @testrunnz The History of Scrum 1939 Shewhart Cycle - Walter Shewhart 1980 39 1930 1940 1950 1960 1970 1990 2000 2010 2020

testrun. co. nz @testrunnz 1939 Shewhart Cycle Walter Shewhart � Specification � Production Source: “Evolution of the PDCA Cycle” Ronald Moen, Clifford Norman � Inspection

testrun. co. nz @testrunnz The History of Scrum 1939 Shewhart Cycle - Walter Shewhart 1950 New Shewhart Cycle - Walter Shewhart 1980 39 1930 1940 1950 1960 1970 1990 2000 2010 2020

testrun. co. nz @testrunnz 1950 New Shewhart Cycle Walter Shewhart � � Specification Production � Inspection � Specification Inspection Production � Source: “Evolution of the PDCA Cycle” Ronald Moen, Clifford Norman � ✓ ✗

testrun. co. nz @testrunnz The History of Scrum 1939 Shewhart Cycle - Walter Shewhart 1950 New Shewhart Cycle - Walter Shewhart 1950 Plan-Do-Check-Act - W. Edwards Deming 1980 39 1930 1940 1950 1960 1970 1990 2000 2010 2020

testrun. co. nz @testrunnz 1950 Plan-Do-Check-Act W. Edwards Deming Inspect & Adapt � � Plan Do Act Check � Source: “Evolution of the PDCA Cycle” Ronald Moen, Clifford Norman �

testrun. co. nz @testrunnz The History of Scrum 1939 Shewhart Cycle - Walter Shewhart 1950 New Shewhart Cycle - Walter Shewhart 1950 Plan-Do-Check-Act - W. Edwards Deming 1980 86 39 1930 1940 1990 1950 1960 1970 1986 “The New Product Development Game” Hirotaka Takeuchi, Ikujiro Nonaka 2000 2010 2020

testrun. co. nz @testrunnz 1986 The 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 Product Development Game” Hirotaka Takeuchi, Ikujiro Nonaka Image: “ST vs Gloucester - Match – 23” by Pierre. Selim - Own work. Licensed under Creative Commons Attribution-Share Alike 3. 0 via Wikimedia Commons.

testrun. co. nz @testrunnz The History of Scrum 1939 Shewhart Cycle - Walter Shewhart 1950 New Shewhart Cycle - Walter Shewhart 1950 Plan-Do-Check-Act - W. Edwards Deming 1980 86 39 1930 1940 1990 1950 1960 1970 1986 “The New Product Development Game” Hirotaka Takeuchi, Ikujiro Nonaka 1993 Jeff Sutherland invents Scrum 2000 93 97 2010 2020

testrun. co. nz @testrunnz The History of Scrum 1939 Shewhart Cycle - Walter Shewhart 1950 New Shewhart Cycle - Walter Shewhart 1950 Plan-Do-Check-Act - W. Edwards Deming 1980 86 39 1930 1940 1990 1950 1960 2000 93 1970 1986 “The New Product Development Game” Hirotaka Takeuchi, Ikujiro Nonaka 1993 Jeff Sutherland invents Scrum 1997 “SCRUM Methodology” - Ken Schwaber 97 2010 2020

testrun. co. nz @testrunnz 1997 SCRUM Methodology Ken Schwaber Inspect & Adapt Sprint � Planning & System Architecture � Develop Wrap Adjust Review � Source: “Scrum Development Process” Ken Schwaber Closure �

testrun. co. nz @testrunnz The History of Scrum 1939 Shewhart Cycle - Walter Shewhart 1950 New Shewhart Cycle - Walter Shewhart 1950 Plan-Do-Check-Act - W. Edwards Deming 1980 86 39 1930 1940 1990 1950 1960 2000 93 1970 1986 “The New Product Development Game” Hirotaka Takeuchi, Ikujiro Nonaka 1993 Jeff Sutherland invents Scrum 1997 “SCRUM Methodology” - Ken Schwaber 1999 “Scrum Framework” ~ Jeff Sutherland 97 99 2010 2020

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

testrun. co. nz @testrunnz 1950 Plan-Do-Check-Act W. Edwards Deming Plan Do � � Act � Plan Do Act Check � Check

testrun. co. nz @testrunnz The History of Scrum 1939 Shewhart Cycle - Walter Shewhart 1950 New Shewhart Cycle - Walter Shewhart 1950 Plan-Do-Check-Act - W. Edwards Deming 1980 86 39 1930 1940 1990 1950 1960 2000 93 97 99 01 1970 1986 “The New Product Development Game” Hirotaka Takeuchi, Ikujiro Nonaka 1993 Jeff Sutherland invents Scrum 1997 “SCRUM Methodology” - Ken Schwaber 1999 “SCRUM Framework” ~ Jeff Sutherland 2001 “Manifesto for Agile Software Development” 2010 2020 13

testrun. co. nz @testrunnz 2001 Manifesto for Agile Software Development Why When Where How What To find a common ground on better software development and in writing February 11 -13, 2001 The Lodge at Snowbird ski resort in the Wasatch mountains of Utah By talking, skiing and relaxing They produced the Agile Software Development Manifesto We value the following items on the left more than the right. However the right still has value. Individuals and interactions over processes and � tools software over comprehensive � Working documentation � Customer collaboration over contract negotiation � Responding to change over following a plan Source: http: //www. agilemanifesto. org/ Who 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

testrun. co. nz @testrunnz The History of Scrum 1939 Shewhart Cycle - Walter Shewhart 1950 New Shewhart Cycle - Walter Shewhart 1950 Plan-Do-Check-Act - W. Edwards Deming 1980 86 39 1930 1940 1990 1950 1960 2000 93 2010 97 99 01 1970 1986 “The New Product Development Game” Hirotaka Takeuchi, Ikujiro Nonaka 1993 Jeff Sutherland invents Scrum 1997 “SCRUM Methodology” - Ken Schwaber 1999 “SCRUM Framework” ~ Jeff Sutherland 2001 “Manifesto for Agile Software Development” 2013 “The Scrum Guide™” ~ Ken Schwaber & Jeff Sutherland 2020 13

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

testrun. co. nz @testrunnz Scrum Now 1939 Shewhart Cycle - Walter Shewhart 1950 New Shewhart Cycle - Walter Shewhart 1950 Plan-Do-Check-Act - W. Edwards Deming 1980 86 39 1930 1940 1990 1950 1960 2000 93 2010 97 99 01 2020 13 1970 1986 “The New Product Development Game” Hirotaka Takeuchi, Ikujiro Nonaka 1993 Jeff Sutherland invents Scrum 1997 “SCRUM Methodology” - Ken Schwaber 1999 “SCRUM Framework” ~ Jeff Sutherland 2001 “Manifesto for Agile Software Development” 2013 “The Scrum Guide™” ~ Ken Schwaber & Jeff Sutherland 2015 Now

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

testrun. co. nz @testrunnz Quick Quiz � What are three roles in Scrum? ☐ The Team member ☐ Project Manager ☐ Scrum Manager ☐ Product Owner ☐ The Development Team ☐ Project Owner ☐ Development Owner ☐ Tester ☐ Scrum Master Source: 2013 “The Scrum Guide™” ~ Ken Schwaber & Jeff Sutherland

testrun. co. nz @testrunnz Quick Quiz � What are three roles in Scrum? ☐ The Team member ☐ Project Manager ☐ Scrum Manager ✓ Product Owner ☐ ✓ The Development Team ☐ ☐ Project Owner ☐ Development Owner ☐ Tester ✓ Scrum Master ☐ Source: 2013 “The Scrum Guide™” ~ Ken Schwaber & Jeff Sutherland

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

testrun. co. nz @testrunnz Quick Quiz � Product Backlog Refinement can take up what percentage of a Sprint? 10% Source: 2013 “The Scrum Guide™” ~ Ken Schwaber & Jeff Sutherland

testrun. co. nz @testrunnz User Story ID Priority Story Points As I want Acceptance Criteria ☐ ☐ so that ☐ ☐ ☐ XS S M L XL XXL 1 3 6 16 40 100

testrun. co. nz @testrunnz User Story A user story is produced by the product owner 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) Acceptance Criteria ID Priority Story Points XS S M L XL XXL 1 3 6 16 40 100 ☐ The user story title will be ten words or less. ☐ A user story will have the format: As a <role>, I want <something achieved> so that <benefit> ☐ 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

testrun. co. nz @testrunnz Hours Sprint Burndown Days 1 2 3 4 5 6 7 8 9 10

testrun. co. nz @testrunnz Story Points Product Burndown for Sprint 1 2 3 4 5 6 7 8 9 10

@testrunnz testrun. co. nz

@testrunnz testrun. co. nz

@testrunnz testrun. co. nz

@testrunnz testrun. co. nz