AGILE & SCRUM
A REFERENCE
MANIFESTO
Individuals and interactions
over processes and tools
Working so!ware over
comprehensive documentation
Customer collaboration over
contract negotiation
Responding to change over
following a plan
3 PILLARS OF THE
EMPIRICAL PROCESS
Transparency
Inspection
Adaptation
PRINCIPLES
Our highest priority is to satisfy
the customer through early and
continuous delivery of valuable
so!ware.
Continuous attention to technical
excellence and good design
enhances agility.
At regular intervals, the team
reflects on how to become more
effective, then tunes and adjusts its
behavior accordingly.
Simplicity–the art of maximizing the
amount of work not done–is
essential.
Build projects around motivated
individuals. Give them the
environment and support they
need, and trust them to get the job
done.
Agile processes promote
sustainable development. The
sponsors, developers, and users
should be able to maintain a
constant pace indefinitely.
SCRUM VALUES
FOCUS COMMITMENT
COURAGE
Deliver working so!ware
frequently, from a couple of
weeks to a couple of months,
with a preference to the
shorter timescale.
Working so!ware is the primary
measure of progress.
The most efficient and effective
method of conveying
information to and within a
development team is face-to-
face conversation.
The best architectures, require-
ments, and designs emerge from
self-organizing teams.
Business people and developers
must work together daily
through-out the project.
Welcome changing require-
ments, even late in development.
Agile processes harness change
for the customer's competitive
advantage.
RESPECT
OPENNESS
THE SCRUM TEAM
Base unit in Scrum consisting of a Scrum Master, a Product Owner,
and Developers. No sub-teams or hierarchies. Cross-functional and
Self-Managing (Typically 10 or fewer people).

Developers Product Owner Scrum Master

Everyone needed to produce the
product. They create a plan for the Sprint,
own quality, modify their plan as needed,
and hold each other accountable as
professionals
Maximizes the value of the product. They
create and communicate the Product Goal
and the Product Backlog Items. They order
the Product Backlog items.
Accountable for establishing Scrum as
defined in the Scrum Guide. They are
the process expert on the team. They
serve the Scrum Team and the
organization

EVENTS ARTIFACTS

The Sprint PRODUCT BACKLOG: An emergent, ordered list of what is

The heartbeat of Scrum. The Sprint contains all the other
events and there is no space between sprints.
! Everyone
" One month or less
# Potentially Shippable Product Increment
Sprint Planning
The first event in the Sprint. The Scrum Team addresses
three topic: Why is this Sprint Valuable? What can be done
in this Sprint? How will the chosen work get done?
! Scrum Team
" Up to 8 hours for a 1-month sprint
# A Sprint Goal and the Product Backlog
needed to improve the product. It is the single source of work
undertaken by the Scrum Team. The Product Owner has final
say on the Product Backlog. Product Backlog refinement is the
act of breaking down and further defining Product Backlog
items into smaller more precise items.
COMMITMENT: PRODUCT GOAL: Describes a future state of
the product which can serve as a target for the Scrum Team to
plan against.
SPRINT BACKLOG: Composed of the Sprint Goal (why), the set
of Product Backlog items selected for the Sprint (what), as well
as an actionable plan for delivering the Increment (how).
COMMITMENT: SPRINT GOAL: The single objective for the
Sprint.

INCREMENT: A concrete stepping stone toward the Product

Daily Scrum Goal.
Inspect progress toward the Sprint Goal and adapt the
Sprint Backlog as necessary. The event is designed for COMMITMENT: DEFINITION OF DONE: A formal description
the Developers and the format is chosen by them. of the state of the Increment when it meets the quality
! Developers, Scrum Master, and Product Owner (optional) measures required for the product.
" Up to 15 minutes
# A plan for the next 24 hours

Sprint Review
Sprint Retrospective
Inspect the outcome of the Sprint and determine future
adaptations. The Scrum Team presents the results of their Plan ways to increase quality and
work to key stakeholders and progress toward the Product effectiveness. The Scrum Team
Goal is discussed. Feedback from customers & stakeholders discusses how the Sprint went and
is provided to the Scrum Team. identifies the most helpful changes
to improve its effectiveness.
! Scrum Team and stakeholders as appropriate
" Up to 4 hours for a 1-month sprint ! Scrum Team
# Updated Product Backlog items based on feedback received " Up to 3 hours for a 1-month sprint