Scrum Cheat Sheet

Scrum approach – Iterative and incremental

Scrum is a lightweight framework that helps people, teams and
organizations generate value through adaptive solutions for
complex problems.

Empirical Scrum pillars

Transparency Inspection Adaptation Scrum va ues l

The emergent process and
work must be visible to those
performing and receiving the
work.
Scrum artifacts progress If any aspects of a process
Commitment
toward agreed goals must be deviate outside acceptable
Focus
inspected frequently and limits or if the resulting
Openness
diligently (to detect potentially product is unacceptable, the
Respect
undesirable variances or process or materials must be
Courage
problems). adjusted.

Scrum Team

A cohesive unit of self- Developers Product Owner Scrum Master

managing professionals
focused on one objective at a People in the Scrum Team Accountable for maximizing Accountable for establishing
time, the Product Goal.

who are committed to the value of the product Scrum as defined in the
creating any aspect of a resulting from the work of the Scrum Guide within the team
Composed of 1 Scrum usable Increment each Sprint.

 Scrum Team. 

 and the organization. 


Master, 1 Product Owner and
Developers. Typically, 10 Delivers a Product Delivers value and manages Facilitates Scrum
people or less. increment. the Product Backlog. implementation.

Scrum Events

T he Sprint Current Sprint 24

A fixed length event of one month or less where work is performed to achieve the Sprint Goal which is a
concrete step toward the Product Goal. Includes 4 formal events - Sprint Planning, Daily Scrums, Sprint
Review, and Sprint Retrospective.

All Scrum events are time-boxed, values written below are recommended for a 4-week Sprint.

Sprint Planning Daily Scrum

Sprint Planning initiates the Sprint by laying out the work to be A short daily meeting to inspect progress toward the Sprint
performed for the Sprint and determining the Sprint Goal.

Goal and adapt the Sprint Backlog as necessary, adjusting the

upcoming planned work.
Addresses 3 topic

Why is this Sprint valuable? Participants – Developers

What can be Done this Sprint? Duration – 15 minutes or less

How will the chosen work get done? Result – Sprint Backlog adjustments

Sprint Retrospective
Participants – the Scrum Team

Duration – up to 8 hours
The last event of the Sprint held to to plan ways to increase

Result – Sprint Backlog quality and effectiveness in the upcoming Sprints.

Topics discusse

What went well during the Sprint,

Sprint Review What problems it encountered

How those problems were (or were not) solved.

An event held at the end of the Sprint to inspect the outcome
How to improve the effectiveness of results?
with key stakeholders and determine future adaptations.

Participants – the Scrum Team

Participants – the Scrum Team and key stakeholders

Duration – up to 3 hours

Duration – up to 4 hours
Result – Impactful improvements to be adressed as soon
Result – Product Backlog adjustments as possible. May be added to the next Sprint’s Backlog.

Scrum Artifacts

Product Backlog Sprint Backlog Product Increment

An emergent, ordered list of A plan by and for the A Concrete stepping stone
what is needed to improve Developers on what work they toward the Product Goal. It is
the product. plan accomplish during the not just what you did last
Sprint to achieve the Sprint Sprint. It is the whole product.

Goal.
Commitment – Definition of
Commitment – Product Goal Commitment – Sprint Goal
Done

Product Goal Sprint Goal Definition of Done B rought to you by:

Describes a future state of the
product which can serve as a
target for the Scrum Team to
plan against.
Its the single objective for the
Sprint.
A formal description of the
state of the Increment when it
meets the quality measures
required for the product.
www.teamhood.com