product
backlog sprint
planning sprint
backlog
product owner Developers 1-4 WEEK
SPRINT
24 HOURS
scrum master
sprint
review
sprint
retro
Developers
THE
SCRUM
SPRINT burndown
charts
Increment
Daily Scrum
www.LearnManagementOnline.com - ScrumStudent.com
Scrum in a nutshell
1. Product Owner orders Product Backlog.
2. Scrum team chooses a Sprint Goal and
tasks from Product Backlog to be developed
during the next Sprint in Sprint Planning.
3. Scrum Team and stakeholders inspect the
increments created (Sprint Review) and
determine future adaptations for the next
Sprints.
4. The Scrum Team review their effectiveness
and quality (Sprint Retrospective) and make
adjustments for the next Sprints. The process
repeats.
Scrum Team
scrum master product owner Developers
Coaches Scrum
Causes removal of
Impediments
Value Maximizer Create any aspect of
a usable Increment
each Sprint
NOTE: The Scrum Team is limited to 10 or fewer members.
Self-managed
Internally decides who
does what, when, and how.
Cross-functional
Members have all the skills
necessary to create value
each Sprint.
Scrum Team
No hierarchies
It is a cohesive unit of
professionals aligned to
the same goals
Collective
Accountability
Holding each other
accountable as
professionals.
NOTE: The Scrum Team is limited to 10 or fewer members.
Scrum Events
Sprint - max 1 calendar month.
Goal is to produce usable
Increments at the end of the
Sprint.
sprint
planning
1-4 WEEK
SPRINT
Max 15 minutes.
For the Developers only.
To monitor progress towards
the Sprint Goal
Daily Scrum
sprint
review
sprint
retro
Max 8 hours (Usually shorter
for shorter Sprints).
The Sprint Goal is agreed upon.
Max 4 hours (Usually shorter
for shorter Sprints).
For Scrum Team and Key
Stakeholders.
To review increments and
determine what is next.
Max 3 hours (Usually shorter
for shorter Sprints).
For the Scrum Team.
Discuss improvements to
effectiveness and quality.
No changes are made that would endanger the
Sprint Goal
The Product Backlog is refined as needed
1-4 WEEK
SPRINT
During the Sprint
Quality goals do not decrease
Scope may be clarified and renegotiated between
the Product Owner and Developers as more is
learned.
Only the Product Owner can cancel the Sprint.
Developers track progress in Daily Scrums
Scrum Artifacts
The Product Backlog is the single source of work undertaken by the
Scrum Team. The Commitment to the Product Backlog is the Product
Goal.
product
backlog
sprint
backlog
Increment
The Sprint Backlog is a set of product backlog tasks that have been
chosen to be developed during the next Sprint to meet the Sprint Goal.
The Commitment to the Sprint Backlog is the Sprint Goal.
An Increment is a concrete stepping stone toward the Product Goal, by
completing product backlog tasks during a Sprint.
The Commitment to the Increment is the Definition of Done.
The Definition of Done lists the agreed quality standards of increments.
Scrum Artifacts
Only Ever One Product
Backlog
Only One Product Goal
Items estimated by
Developers
Continuous refinement
by the Scrum Team
Product Owner’s
accountability.
product
backlog sprint
backlog Increment
A plan by and for the
Developers
Updated throughout the
Sprint
Developer’s
accountability
Each Increment is
additive to all prior
Increments.
Multiple Increments may
be created within a
Sprint.
Should meet the
Definition of Done.
Definition of Done
Is a list of conditions that must be true in order to
consider Increments truly done.
Defined by the Organization if available
If not, must be mutually defined by Scrum Teams.
Transparency
Inspection
Adaption
SCRUM
Inspection - Frequent checks on
progress towards goals, to detect
deviations from the path to the goal.
Transparency - Making work and
outputs clear and visible
Adaption -Adjusting the process as
soon as possible to minimize any
further deviation or issues.
3 Pillars of Scrum
“Founded on Lean Thinking and
Empiricism“
S
c
r
u
m
V
a
l
u
e
s
Courage
Scrum Team members have the courage to do
the right thing and work on tough problems.
Focus
Everyone focuses on the work of the Sprint and
the goals of the Scrum Team.
Commitment
People personally commit to achieving the
goals of the Scrum Team.
Respect
Scrum Team members respect each other to be
capable, independent people.
Openness
The Scrum Team and its stakeholders agree to
be open about all the work and the challenges
with performing the work.
Scrum.com - Nexus Guide
Scaled Scrum
Multiple Scrum Teams working
together to create an Integrated
Increment
A Nexus Integration Team is needed.
Don’t need to Synchronize Sprints
between teams
Managing dependencies is key
One Product Owner, One Product
Backlog, One Product Goal at all times!
Scrum.com - Nexus Guide
