Printouts for ScrumMaster.dk
Printouts for ScrumMaster.dk
Scrum Education
Scrum Education
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidelines and tips
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Scrum Methodology: A Comprehensive Guide to Agile Project Management, Slides of Communication
Ensures that people do what they committed to do. The Team works on the selected Backlog Items. The Team updates the Sprint Backlog and report impediments.
Typology: Slides
2022/2023
1 / 61
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download Scrum Methodology: A Comprehensive Guide to Agile Project Management and more Slides Communication in PDF only on Docsity!
Printouts for ScrumMaster.dkPrintouts for ScrumMaster.dk
Scrum EducationScrum Education
Cynefin - introducing ComplexityCynefin - introducing Complexity
Dave Snowden
Zone of complacency.
Over-reliance on
structure, risk of
catastrophic failure
Ordered, cause and
effect. Any reasonable
person can see how
this can be solved
Ordered, cause and
effect, but difficult.
Analysis or experts
are required.
Order can be seen in
retrospect. Emerging
knowledge, safe-to-
fail experiments.
No order to be seen.
Action to stabilize is
required.
Disorder, missing
perception of actual
domain, people react
as they are used to
In the Complex
Domain
Probe, sense,
respond.
Create environ-
ments and
expe-riments
that allow
patterns to
emerge
Increase levels
of interaction
and
communication
Use methods
that can help
generate ideas
Encourage
dissent and
diversity
Manage
starting
conditions
and monitor for
emergence
Managed dive into
shallow chaos,
innovation, relaxing
constraints
Experimentation,
prototypes, holding
options open as long
as possible
The Scrum FlowThe Scrum Flow
(^22)
The Scrum FlowThe Scrum Flow
Sprint backlog Improvement Backlog
To do Progress Done
Sprint backlog
To do Progress Done
Product
Backlog
Refnement
Sprint
Planning
Sprint
Planning
Sprint
Review
Daily
Scrum
Sprint
Retrospective
Product
Increment
Idea &
Vision
Product Owner. Responsible for
business value, ROI and
prioritization. Owns Product Backlog
product backlog
Next
++
Out of scope
New
product backlog
Next
++
Out of scope
New
Product Backlog
Ordered list of
requirements
Scrum Master.
Responsible for pro-
cess and removing
impediments. Owns
Impediment Backlog Team. Responsible for
creating product and results.
Owns Sprint Backlog
Selected Backlog
Product/Release Burndown
Sprints
Remain
Ideal
Ideal
P o in ts
600
500
400
300
200
100
0
1 2 3 4 5 6 7 8 9
Product/Release Burndown
Sprints
Remain
Ideal
Ideal
P o in t s
600
500
400
300
200
100
0
1 2 3 4 5 6 7 8 9
Sprint Burndown
Days
Remaining
Ideal
T a s k s (^) L e f t
60
6 7 8 9
50
5
40
4
30
3
20
2
10
1
0
Sprint Burndown
Days
Remaining
Ideal
T a s k s L e f t
60
6 7 8 9
50
5
40
4
30
3
20
2
10
1
0
Stakeholders. Users, Customers,
Management. Input to Product
Backlog, participate and help
Schwaber and SutherlandSchwaber and Sutherland
The Scrum Flow, German versionThe Scrum Flow, German version
Roles Artifacts Meetings Organizational Process
Scrum Master
Responsible for
process and
removing
impediments
Team
Responsible
for creating
product and
results,
manages
sprint
backlog
Management/Users/
Stakeholders
Observe and advise, input to
Product Backlog, help remove
impediments
Product Backlog
List of requirements &
issues, user stories
Owned by Product Owner.
Anybody can add to it
Only Product Owner prioritizes
Product burn-down chart
Sprint Backlog
Sprint Goal: One-sentence
summary. List of tasks
Showing status’ of tasks
Owned by Team
Only Team modifies it
Possibly extend with
Burndown
Updated daily
Impediment Backlog
List of obstacles & unmade
decisions.
Owned by Scrum Master.
Updated daily.
Sprint Planning
2 * 2-4 hours, estimates MUST be ready.
#1, In: Product Backlog, existing product,
business and technology conditions.
Select highest priority items in Product
Backlog; declare Sprint Goal.
#2: Team turns selected items into Sprint
Backlog and breaks down to tasks.
Out: Sprint Backlog/Task board.
Backlog Refinement
Daily Scrum
Same time and place every day, 15 min.
For the Team, all can attend, only Team and
Scrum Master speak, questions:
- What did you accomplish yesterday? 2)
What will you accomplish today? 3) What is in
your way? Any obstacles?
Team updates Sprint Backlog, Scrum- Master
updates Impediment Backlog
Sprint Review
Informal, 2-4 hours, informational, attended
by all. All discuss and review
Only completed results/functionality can be
presented.
Sprint Retrospective
Team and Scrum Master. What did we
experience? What went well? What can be
improved?
Decide, take responsibility and action.
Initial Vision
More on
Backlog +
budget?
Sprint Planning
Daily work
Update Sprint
Backlog
Daily Scrum
Days < Sprint
length
Sprint Review
Sprint Retrospective
Done
Product Owner
Responsible for
vision, business
value, prioritization
and Product Backlog
Sprint
No
Yes
No
Yes
No
No
The Scrum Activities (Ceremony)The Scrum Activities (Ceremony)
■ The Sprint Planning Meeting #1The Sprint Planning Meeting
■ Time-boxed 2-4 hours. Team, Product Owner and Scrum MasterTime-boxed 2-4 hours. Team, Product Owner and Scrum Master
■ (^) The purpose is to select items from the Product Backlog for the next SprintThe purpose is to select items from the Product Backlog for the next Sprint
■ (^) Product Owner has made sure relevant items are estimated, he hasProduct Owner has made sure relevant items are estimated, he has
prioritized items and formulated a Sprint Goalprioritized items and formulated a Sprint Goal
■ The Team’s has assessed their resources and capacityThe Team’s has assessed their resources and capacity
■ (^) Product Owner works on raising the Team’s understanding of the items onProduct Owner works on raising the Team’s understanding of the items on
the Product Backlog. Estimates of Backlog Items may changethe Product Backlog. Estimates of Backlog Items may change
■ In dialogue with the Team the best possible set of items are selectedIn dialogue with the Team the best possible set of items are selected
■ The Sprint Planning Meeting #2The Sprint Planning Meeting
■ (^) Time boxed 2-4 hours. Team and Scrum MasterTime boxed 2-4 hours. Team and Scrum Master
■ (^) The purpose is to decide, how to deliver the selected Product Backlog Items.The purpose is to decide, how to deliver the selected Product Backlog Items.
Each Product Backlog Item is analyzed, then designed and broken down toEach Product Backlog Item is analyzed, then designed and broken down to
tasks. No task should last more than 1 day,tasks. No task should last more than 1 day,
■ The Sprint Backlog is built. The final Sprint Backlog is made public. This is theThe Sprint Backlog is built. The final Sprint Backlog is made public. This is the
Team’s commitmentTeam’s commitment
■ The Daily ScrumThe Daily Scrum
■ Time-boxed to 15 min. Daily synchronization by Team and Scrum Master,Time-boxed to 15 min. Daily synchronization by Team and Scrum Master,
held same place, same time, every working dayheld same place, same time, every working day
■ Anyone can come, but only Team and Scrum Master speakAnyone can come, but only Team and Scrum Master speak
■ 3 questions asked to everybody:3 questions asked to everybody:
■ (^) What have you accomplishedWhat have you accomplished
since the last Daily Scrum?since the last Daily Scrum?
■ What will you accomplish untilWhat will you accomplish until
the next Daily Scrum?the next Daily Scrum?
■ (^) Does anything prevent youDoes anything prevent you
from working optimally?from working optimally?
■ Sprint ReviewSprint Review
■ (^) Time-boxed to maximum 2-4 hours. The Team presents itsTime-boxed to maximum 2-4 hours. The Team presents its
accomplishments in the Sprint. Only finished Backlog Items (“Done”) areaccomplishments in the Sprint. Only finished Backlog Items (“Done”) are
presentedpresented
■ (^) Product Owner and Stakeholders invited so they can know ”where we are”Product Owner and Stakeholders invited so they can know ”where we are”
in the projectin the project
■ (^) The audience asks questions, makes comments and identify things missingThe audience asks questions, makes comments and identify things missing
or different – plus new ideas. All goes to the Product Backlogor different – plus new ideas. All goes to the Product Backlog
■ Sprint RetrospectiveSprint Retrospective
■ (^) Time-boxed to maximum 2-4 hours. The Team and the Scrum MasterTime-boxed to maximum 2-4 hours. The Team and the Scrum Master
review the Sprintreview the Sprint
■ (^) The six step approach: 1. Is everyone OK with talking openly? 2. Create aThe six step approach: 1. Is everyone OK with talking openly? 2. Create a
timeline of the Sprint and each tell a story of importance. 3. Ask – Whattimeline of the Sprint and each tell a story of importance. 3. Ask – What
went well? 4. Ask – What could be improved? 5. Ask – Who is in control? 6.went well? 4. Ask – What could be improved? 5. Ask – Who is in control? 6.
Create and agree on an action listCreate and agree on an action list
■ Performing a SprintPerforming a Sprint
■ (^) Sprints are 2, 3 or 4 weeks longSprints are 2, 3 or 4 weeks long
■ (^) The Team self-organizes within constraints, splits the work among theThe Team self-organizes within constraints, splits the work among the
members, they ask for help and guidance, if needed, they use the Scrummembers, they ask for help and guidance, if needed, they use the Scrum
Master as a facilitator and bufferMaster as a facilitator and buffer
■ (^) Assign a Sprint area, if possible a separate room. Let the team have theAssign a Sprint area, if possible a separate room. Let the team have the
necessary resources. Assign a budget per Sprintnecessary resources. Assign a budget per Sprint
■ The Team is set free to fulfill its commitment in the SprintThe Team is set free to fulfill its commitment in the Sprint
■ Backlog Refinement and EstimationBacklog Refinement and Estimation
■ (^) Time-boxed to maximum 2-4 hours, or maybe two meetingsTime-boxed to maximum 2-4 hours, or maybe two meetings
■ (^) Product Owner has selected possible items for next Sprint. New ideas thatProduct Owner has selected possible items for next Sprint. New ideas that
need to be discussed. The Team estimates. Detailed requirement analysis.need to be discussed. The Team estimates. Detailed requirement analysis.
Breaking down of Epics (Large stories)Breaking down of Epics (Large stories)
■ The Backlog Refinement meeting is a preparation for Sprint Planning #1The Backlog Refinement meeting is a preparation for Sprint Planning #
meetingmeeting
The Scrum ArtifactsThe Scrum Artifacts
Estimate EU Country PopulationEstimate EU Country Population
Source: http://en.wikipedia.org/wiki/List_of_European_countries_by_population
NO
SE
DK
UK
DK
NL
FR
PL
DE
ES
PT
Country Population
Population
Diff * diff
DK (5.6) 2 2 0
NL
NO
FR
UK
PL
ES
PT
SE
DE
Sum
Buffered
sum
SQRT:
Estimate US State PopulationEstimate US State Population
State Population
Population
Diff * diff
MA (6.69) 5 5 0
FL
CT
IA
CA
NY
MT
NJ
PA
IN
Sum
Buffered
sum
SQRT:
Estimate Distance from OsloEstimate Distance from Oslo
One more reference: Hønefoss is “1”
Source: Google Maps
Estimate Indian State PopulationEstimate Indian State Population
One more reference: Tripura is “1”
Source: http://en.wikipedia.org/wiki/List_of_states_and_union_territories_of_India_by_population
As per census data 2011, the total population
of India is: 1,210,193,