Upload
maximillian-hutchinson
View
216
Download
0
Tags:
Embed Size (px)
Citation preview
http://www.testrun.co.nz/presentations.html
Scrum(software development)
http://www.testrun.co.nz/presentations.html
Scrum(software development)
Why
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…
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 peopleproductively
valueproductsdeliveringcreatively
problemscomplexadaptive
http://www.testrun.co.nz/presentations.htmlSource: “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
http://www.testrun.co.nz/presentations.html
Scrum was designed to increase productivity and improve qualitythrough teamwork.
Source: “Scrum in Church, Saving the World One Team at a Time” 2009 Arline Sutherland, Jeff Sutherland, Christine Hegarty
ScrumWhy
http://www.testrun.co.nz/presentations.htmlSource: “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 qualitythrough teamwork.
Why
http://www.testrun.co.nz/presentations.html
The History of Scrum
1930 1940 1950 1960 1970
1980 1990 2000 2010 2020
1939 Shewhart Cycle - Walter Shewhart
39
http://www.testrun.co.nz/presentations.html
Specification Production Inspection
Source: “Evolution of the PDCA Cycle” Ronald Moen, Clifford Norman
1939 Shewhart CycleWalter Shewhart
http://www.testrun.co.nz/presentations.html
The History of Scrum
1930 1940 1950 1960 1970
1980 1990 2000 2010 2020
1939 Shewhart Cycle - Walter Shewhart
39
1950 New Shewhart Cycle - Walter Shewhart
http://www.testrun.co.nz/presentations.html
1950 New Shewhart CycleWalter Shewhart
Specification Production Inspection ✗
✓
Source: “Evolution of the PDCA Cycle” Ronald Moen, Clifford Norman
Specification
ProductionInspection
http://www.testrun.co.nz/presentations.html
The History of Scrum
1930 1940 1950 1960 1970
1980 1990 2000 2010 2020
1939 Shewhart Cycle - Walter Shewhart
1950 Plan-Do-Check-Act - W. Edwards Deming
39
1950 New Shewhart Cycle - Walter Shewhart
http://www.testrun.co.nz/presentations.html
Do
CheckAct
Plan
1950 Plan-Do-Check-ActW. Edwards Deming
Source: “Evolution of the PDCA Cycle” Ronald Moen, Clifford Norman
Learn & Adapt
http://www.testrun.co.nz/presentations.html
The History of Scrum
1930 1940 1950 1960 1970
1980 1990 2000 2010 2020
1939 Shewhart Cycle - Walter Shewhart
1950 Plan-Do-Check-Act - W. Edwards Deming
1986 “The New New Product Development Game”
Hirotaka Takeuchi, Ikujiro Nonaka
8639
1950 New Shewhart Cycle - Walter Shewhart
http://www.testrun.co.nz/presentations.html
1986 The New New Product Development
GameHirotaka 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 NonakaImage: “ST vs Gloucester - Match – 23” by PierreSelim - Own work. Licensed under Creative Commons Attribution-Share Alike 3.0 via Wikimedia Commons.
http://www.testrun.co.nz/presentations.html
The History of Scrum
1930 1940 1950 1960 1970
1980 1990 2000 2010 2020
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 9739
1950 New Shewhart Cycle - Walter Shewhart
1993 Jeff Sutherland invents Scrum
93
http://www.testrun.co.nz/presentations.html
The History of Scrum
1930 1940 1950 1960 1970
1980 1990 2000 2010 2020
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
86 9739
1950 New Shewhart Cycle - Walter Shewhart
1993 Jeff Sutherland invents Scrum
93
http://www.testrun.co.nz/presentations.html
1997 SCRUM MethodologyKen Schwaber
Source: “Scrum Development Process” Ken Schwaber
ClosurePlanning & System
Architecture Wrap
ReviewAdjust
Develop
Sprint
Learn & Adapt
http://www.testrun.co.nz/presentations.html
The History of Scrum
1930 1940 1950 1960 1970
1980 1990 2000 2010 2020
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
86 9739
1950 New Shewhart Cycle - Walter Shewhart
1993 Jeff Sutherland invents Scrum
93
1999 “Scrum Framework” ~ Jeff Sutherland
99
http://www.testrun.co.nz/presentations.html
1999 Scrum FrameworkJeff Sutherland
Source: “Scrum: A Pattern Language for Hyperproductive Software Development” Jeff Sutherland
Product
Product Backlog
Daily Scrum15 minutes
What went well?
What did notgo well?
Ideas to Improve
process & product?
Learn & Adapt
24 hours
Sprint
Do
Act
Plan
Sprint1 – 4 weeks
ReviewSprintRetrospective
SprintPlanning
Check
http://www.testrun.co.nz/presentations.html
1950 Plan-Do-Check-ActW. Edwards Deming
Do
CheckAct
Plan
Do
CheckAct
Plan
http://www.testrun.co.nz/presentations.html
The History of Scrum
1930 1940 1950 1960 1970
1980 1990 2000 2010 2020
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
86 9739
1950 New Shewhart Cycle - Walter Shewhart
1993 Jeff Sutherland invents Scrum
93
1999 “SCRUM Framework” ~ Jeff Sutherland
99 13
2001 “Manifesto for Agile Software Development”
01
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 onthe right, we value the items on the left more.Source: http://www.agilemanifesto.org/
Working software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan
Kent BeckMike BeedleArie van BennekumAlistair CockburnWard CunninghamMartin FowlerJames GrenningJim HighsmithAndrew HuntRon JeffriesJon KernBrian MarickRobert C. MartinSteve MellorKen SchwaberJeff SutherlandDave 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.
http://www.testrun.co.nz/presentations.html
The History of Scrum
1930 1940 1950 1960 1970
1980 1990 2000 2010 2020
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
86 9739
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
99 13
2001 “Manifesto for Agile Software Development”
01
http://www.testrun.co.nz/presentations.html
SprintPlanning
SprintReview
SprintRetrospective
2013 The Scrum Guide™Ken Schwaber & Jeff Sutherland
Source: 2013 “The Scrum Guide™” ~ Ken Schwaber & Jeff Sutherland
The Sprint
Sprint1 – 4 Weeks
Daily Scrum15 minutes
Product
What went well?
What did notgo well?
Ideas to Improve
process & product?
Achievementawards?
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
SprintBacklog
Three Questions1. What I did
yesterday?2. What I’ll do today?3. Any impediments?
The ProductOwner
The Development TeamSize 6 ±3 (3 to 9)
The Scrum Master
Definition of “Done”
Definition of “Ready”
Scrum Team
ProductBacklog
RefinementUp to 10%
of Sprint time
Release Burndown
Series1
Monitoring progresstowards a Goal
Sprint Burndown
Series1
Monitoring Sprintprogress
Sprint Goal
Sprint
Backlog
To Do
WIPDon
e
http://www.testrun.co.nz/presentations.html
Scrum Now
1930 1940 1950 1960 1970
1980 1990 2000 2010 2020
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
86 9739
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
99 13
2001 “Manifesto for Agile Software Development”
01
2014
Now
http://www.testrun.co.nz/presentations.html
SprintPlanning
SprintReview
SprintRetrospective
2014 Scrum in 20 seconds
The Sprint
Sprint1 – 4 Weeks
Daily Scrum15 minutes
Product
What went well?
What did notgo well?
Ideas to Improve
process & product?
Achievementawards?
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
SprintBacklog
Definition of “Done”
Definition of “Ready”
Sprint Goal
Source: 2013 “The Scrum Guide™” ~ Ken Schwaber & Jeff Sutherland
ProductBacklog
RefinementUp to 10%
of Sprint time
The ProductOwner
The Development TeamSize 6 ±3 (3 to 9)
The Scrum Master
Scrum Team
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
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
✓
✓
✓
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
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%
http://www.testrun.co.nz/presentations.htmlSource: 2013 “The Scrum Guide™” ~ Ken Schwaber & Jeff Sutherland
Lets Start!
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 401 100
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 <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 storySource: www.mountaingoatsoftware.com Mike Cohn ~ As a <type of user>, I want <some goal> so that <some reason>.
S M L XL
Story Points
Priority
ID
User Story
XS XXL
3 6 16 401 100
http://www.testrun.co.nz/presentations.html
Sprint Burndown
Se-ries1
Hou
rs
Days
1 2 3 4 5 6 7 8 9 10
http://www.testrun.co.nz/presentations.html
Product Burndown for Sprint
Se-ries1
Sto
ry P
oin
ts
Sprint
1 2 3 4 5 6 7 8 9 10