Scrum Origin and definition

Scrum has been developed in the early 1990s. It is a lightweight framework that
helps people, teams and organizations generate value through adaptive solutions
for complex problems.
It is designed for teams of ten or fewer members, who break their work into goals
that can be completed within time-boxed iterations, called sprints, no longer than
one month and most commonly two weeks. The scrum team assess progress
in time-boxed daily meetings of 15 minutes or less, called daily scrums (a form
of stand-up meeting). At the end of the sprint, the team holds two further meetings:
the sprint review which demonstrates the work done to stakeholders to elicit
feedback, and sprint retrospective which enables the team to reflect and improve.
Scrum Theory
Scrum is founded on empiricism and lean thinking. Empiricism asserts that
knowledge comes from experience and making decisions based on what is
observed. Lean thinking reduces waste and focuses on the essentials.

Scrum Theory Pillars-

TRANSPENECY INSPECTION ADAPTATION

 Scrum Values
Successful use of Scrum depends on people becoming more
proficient in living five values:
• Commitment
• Focus
• Openness
• Respect
• Courage
 Scrum Team
Developer

Product Owner

Scrum Master
 Developers
Developers are the people in the Scrum Team that are committed to creating any aspect of
a usable Increment each Sprint.
Developers are always accountable for:
•Creating a plan for the Sprint, the Sprint Backlog;
•Instilling quality by adhering to a Definition of Done;
•Adapting their plan each day toward the Sprint Goal; and,
•Holding each other accountable as professionals.
 Product Owner
The Product Owner is accountable for maximizing the value of the product resulting
from the work of the Scrum Team.
The Product Owner is also accountable for effective Product Backlog management,
which includes:
•Developing and explicitly communicating the Product Goal;
•Creating and clearly communicating Product Backlog items;
•Ordering Product Backlog items; and,
•Ensuring that the Product Backlog is transparent, visible and understood.
 Scrum Master
SCRUM MASTER ROLE TOWARDS SCRUM TEAM SCRUM MASTER ROLE TOWARDS PRODUCT OWNER SCRUM MASTER ROLE TOWARDS ORGANISATION

o Coaching the team members in

o Helping find techniques for o Leading, training, and coaching
self-management and cross-
effective Product Goal definition the organization in its Scrum
functionality;
and Product Backlog management; adoption;
o Helping the Scrum Team focus on
o Helping the Scrum Team o Planning and advising Scrum
creating high-value Increments
understand the need for clear and implementations within the
that meet the Definition of Done;
concise Product Backlog items; organization;
o Causing the removal of
o Helping establish empirical product o Helping employees and
impediments to the Scrum Team’s
planning for a complex stakeholders understand and
progress; and,
environment; and, enact an empirical approach for
o Ensuring that all Scrum events
o Facilitating stakeholder complex work; and,
take place and are positive,
collaboration as requested or o Removing barriers between
productive, and kept within the
needed. stakeholders and Scrum Teams.
timebox.
 Scrum Events
THE SPRINT SPRINT PLANNING DAILY SCRUM

Sprint Planning initiates the Sprint by laying

Sprints are the heartbeat of Scrum, where
ideas are turned into value.
They are fixed length events of one month or
less to create consistency. A new Sprint
starts immediately after the conclusion of the
previous Sprint.
out the work to be performed for the Sprint.
This resulting plan is created by the
collaborative work of the entire Scrum Team.
Sprint Planning addresses the following
topics:
• Topic One: Why is this Sprint valuable?
• Topic Two: What can be Done this Sprint?
• Topic Three: How will the chosen work get
done?
The Daily Scrum is a 15-minute event for
the Developers of the Scrum Team. To
reduce complexity, it is held at the same
time and place every working day of the
Sprint. If the Product Owner or Scrum
Master are actively working on items in the
Sprint Backlog, they participate as
Developers..

SPRINT REVIEW SPRINT RETROSPECTIVE

The purpose of the Sprint Review is to inspect the outcome of the
The purpose of the Sprint Retrospective is to plan
Sprint and determine future adaptations. The Scrum Team
ways to increase quality and effectiveness for next
presents the results of their work to key stakeholders and
sprints.
progress toward the Product Goal is discussed.

Scrum’s artifacts represent work or value. They are designed to maximize transparency of key
information. Thus, everyone inspecting them has the same basis for adaptation.
Product Backlog
The Product Backlog is an
emergent, ordered list of what is
needed to improve the product. It is
the single source of work
undertaken by the Scrum Team.
The Product Goal describes a future
state of the product which can serve
as a target for the Scrum Team to
plan against. The Product Goal is in
the Product Backlog. The rest of the
Product Backlog emerges to define
“what” will fulfill the Product Goal.
Scrum Artifacts
SPRINT BACKLOG PRODUCT INCREMENT
The Sprint Backlog is composed of the
Sprint Goal (why), the set of Product
An Increment is a concrete stepping stone
Backlog items selected for the Sprint
toward the Product Goal. Each Increment is
(what), as well as an actionable plan for
additive to all prior Increments and
delivering the Increment (how).
thoroughly verified, ensuring that all
The Sprint Goal is created during the
Increments work together. Work cannot be
Sprint Planning event and then added to
considered part of an Increment unless it
the Sprint Backlog. As the Developers
meets the Definition of Done.
work during the Sprint, they keep the
Sprint Goal in mind.
 Scrum Process Model

PREPARATIONS Sprint Planning RELEASE

Meeting Daily Scrum or
Daily Work

Update
• Product Owner
▪ Business Case & Funding Product

▪ Contractual Agreement & Vision Backlog • Scrum Master

▪ Initial Product Backlog
SCRUM • Team Members
▪ Initial Release Plan PROCESS Product
Increment • Stakeholders
▪ Stakeholder Buy-in, Assemble Team
• Users

Sprint
Retrospective
Sprint Review
 Scrum Process

Pre-Game Staging Sprint Development Sprints Wrapper Sprints

In a nutshell, Scrum requires a Scrum Master to foster an environment
where:
1.A Product Owner orders the work for a complex problem into a Product
Backlog.
2.The Scrum Team turns a selection of the work into an Increment of
value during a Sprint.
3.The Scrum Team and its stakeholders inspect the results and adjust for
the next Sprint.
4.Repeat