3 3 Artifacts Mechanical Professional

Accounta 5 Events and Scrum PLUS + Commitment Courage Focus Openness Respect Scrum (Sweet
16)
bilities Commits (Ocean’s 11)

Sprint
5 Values
Retrospective C2 FOR

Product
Backlog
“Future work”

Daily Scrum

Backlog
Developers Increment
Refinement Sprint Backlog
“Done Work”
“Current Product
work” Owner

Sprint
Sprint Review
Planning
Product Goal

Definition of
Sprint Goal “Done”
Sprint = a Scrum Master

container for all

other events

Empiricism Transparency Adaptation Inspection

 Product Owner Scrum Master Developers Scrum Team

Are the people in the Scrum

Accountable for establishing Is cross-functional - they have
Maximizes the value of the Team that are committed to
Scrum as defined in the Scrum all the skills necessary to
product creating any aspect of a usable
Guide create value each Sprint.
Increment each Sprint

Not a committee. One person Is self-managing, they

who has the final call about the Is accountable for the Scrum Creates a plan for the Sprint, internally decide who does
ordering of the Product Team’s effectiveness the Sprint Backlog what, when, and how
Backlog

Has final say on the content Coaches the team members in Has no sub-teams or
Instills quality by adhering to a
and ordering of the Product self-management and hierarchies
Definition of Done
Backlog cross-functionality

Develops and explicitly Are true leaders who serve the

Adapts their plan each day Typically 10 or fewer people
communicates the Product Scrum Team and the larger
toward the Sprint Goal
Goal organization

Creates and clearly Serves the Scrum Team, Is accountable for creating a
Hold each other accountable valuable, useful Increment
communicates Product Product Owner, and the
as professionals every Sprint
Backlog items Organization

Ensures that the Product

Are responsible for sizing the
Backlog is transparent, visible
work to be done
and understood

Has the authority to cancel the

Sprint
 Sprint Sprint Planning Daily Scrum Sprint Review Sprint Retrospective

Fixed length events of one

Timeboxed to 8 hours for a Timeboxed to 4 hours for a Timeboxed to 3 hours for a
month or less to create Timeboxed to 15 minutes
one-month Sprint one-month Sprint one-month Sprint
consistency

The purpose is to inspect

A new one starts immediately The purpose is to inspect the The purpose is to plan ways to
progress toward the Sprint
after the conclusion of the The first event of a Sprint outcome of the Sprint and increase quality and
Goal and adapt the Sprint
previous one determine future adaptations effectiveness
Backlog as necessary

Inspect how the last Sprint

Is a working session and the went with regards to
Each of these can be Addresses the topic: Why is Occurs in the same place at
Scrum Team should avoid individuals, interactions,
considered a short project this Sprint valuable? the same time every day
limiting it to a presentation processes, tools, and their
Definition of Done

The whole Scrum Team The Scrum Team and

Improves communications, An opportunity for the Scrum
All the work necessary to collaborates to define a Sprint stakeholders review what was
identify impediments, promotes Team to identify the most
achieve the Product Goal Goal that communicates why accomplished, what has
quick decision-making, helpful changes to improve its
happen within this event the Sprint is valuable to changed, and collaborate on
eliminates other meetings effectiveness
Stakeholders what to do next
The Scrum Team discusses
Focuses on progress toward what went well during the
The purpose of this event is to Addresses the topic: What can the Sprint Goal and produces Is the second to last even of Sprint, what problems it
turn ideas into value be Done this Sprint? an actionable plan for the next the Sprint encountered, and how those
day of work problems were (or were not)
solved
Through discussions with the
Can be canceled if the Sprint
Product Owner, the
Goal becomes obsolete. Only This event is for the Should never be considered a This event concludes the
Developers select items from
the Product Owner has the Developers of the Scrum Team gate to releasing value Sprint
the Product Backlog to include
authority to cancel this
in the current Sprint

Addresses the topic: How will

the chosen work get done?

For each selected PBI, the

Developers plan the work
necessary to create an
Increment that meets the
Definition of Done
 Product Backlog Product Goal Sprint Backlog Sprint Goal Increment Definition of Done

Is composed of the Sprint Goal

Describes a future state of the (why), the set of Product Is a formal description of the
An emergent, ordered list of
product which can serve as a Backlog items selected for the Is the single objective for the Is a concrete stepping stone state of the Increment when it
what is needed to improve the
target for the Scrum Team to Sprint (what), as well as an Sprint toward the Product Goal meets the quality measures
product.
plan against actionable plan for delivering required for the product
the Increment (how)

A commitment by the
It is the single source of work Is additive to all prior ones and The moment a Product
A plan by and for the Developers, it provides
undertaken by the Scrum Lives in the Product Backlog thoroughly verified, ensuring Backlog item meets this, an
Developers flexibility in terms of the exact
Team that all of these work together Increment is born
work needed to achieve it

A highly visible, real-time Creates transparency by

Refinement is the act of The rest of the Product Creates coherence and focus,
picture of the work that the providing everyone a shared
breaking down and further Backlog emerges to define encouraging the Scrum Team In order to provide value, this
Developers plan to accomplish understanding of what work
defining items on this artifact “what” will fulfill this to work together rather than on must be usable
during the Sprint in order to was completed as part of the
into smaller more precise items commitment separate initiatives
achieve the Sprint Goal Increment

Refinement is an ongoing If a Product Backlog item does

Created during the Sprint
activity to add details, such as Is a long-term objective for the Updated throughout the Sprint Multiple of these may be not meet this, it cannot be
Planning event and then added
a description, order, and size Scrum Team as more is learned created within a Sprint released or even presented at
to the Sprint Backlog
to items on this artifact the Sprint Review

If the work turns out to be If part of the standards of the

The Scrum Team must fulfill (or Should have enough detail that different than expected, The sum of these are organization, all Scrum Teams
abandon) this before taking on they can inspect their progress Developers collaborate with presented at the Sprint Review must follow it as a minimum. If
the next in the Daily Scrum the Product Owner to negotiate thus supporting empiricism it is not, the Scrum Team must
scope without affecting this create one for the product

If there are multiple Scrum

Work cannot be considered Teams working together on a
part of this unless it meets the product, they must mutually
Definition of Done define and comply with the
same version of this