What is Scrum?

The most common Agile method

The Scrum framework consists of Scrum teams and their associated roles,
events, artifacts, and rules. Each component within the framework serves
a specific purpose and is essential to Scrums success and usage.
A framework within which people can address complex problems, while
productively and creatively delivering product of highest possible value.
The greatest potential benefit of Scrum is for complex work involving
knowledge creation, and collaboration.
Teams are responsible for creating and adapting their processes within
this framework.
Scrum attempts to build a potentially shippable (properly tested) product
increment every iteration.
Scrum uses fixed-length iterations, called sprints, which are typically 2-4
weeks long.

Scrum Origin

Ken
Schwaber

Jeff
Sutherland

Ken Schwaber and Jeff Sutherland wrote the Scrum Guide. Together,
they stand behind the Scrum Guide, which can be downloaded in
multiple languages from http://www.scrum.org/Scrum-Guides

Scrum Pillars

Transpare
ncy

Inspection

Adaptatio
n

Scrum Cycle Summary

PRODUC
T VISION

DAILY
SCRUM

WORKING
DAYS

High Priority

SPRINT
2-4 Weeks

Low Priority

SPRINT
BACKLOG
PLANNING
PRODUCT BACKLOG

REVIE
W

RETROSPECT
IVE

FINAL
PRODUCT
ACCEPTED
PROJECT
COMPLETE

SHIPPABLE
PRODUCT
INCREMENT

Scrum Cycle Summary

1.Product owner updates the requirements in the prioritized list, called
product backlog
2.The product owner and development team get together for the
sprint planning meeting and generate the sprint backlog. What will be
done and how it will be done in this development cycle(Sprint)
3.The development team does the development work of the product
increment that has been planned, aiming to meet the Sprint goals
4.Every day, the development team holds the daily scrum, a 15-minute
meeting which aims to promote visibility and communication between
team members.

Scrum Cycle Summary

5. At the end of the development cycle, the development team will
have produced a product increment which is done, meaning value
for the customer.
6. Then the development team meets the product owner and
stakeholder for the sprint review and presents to them what was
produced during the sprint
7. Right after the review meeting, the Scrum team holds the sprint
retrospective, where it discusses what happened and what could
be improved for future sprints.
8. And a new cycle starts until the final product is produced/project

Scrum Roles
Product
Owner

Ensure and
maximized the
ROI for the
customer from
the work of the
Team.

Scrum
Master

Ensures that the

value, practices
and rules of
Scrum are
understood and
followed.

Development
Team

Generates value for

the customer,
building high quality
product increments.

Product Owner

Ensures and maximizes the profit/return on investment (ROI) for

customer
Responsible for product vision
Business value driver
Sets project priorities, decides what will be built and in which order
Defines the features of the project or desired outcome of the project
Chooses release date and content
Available to the team
Vision keeper
Heat shield
Accepts or rejects work results

Scrum Master & Product Owner:

Finding techniques for effective product backlog
management
Clearly communicating vision, goals, and product
backlog items to the development team
Teaching the Scrum team to create clear and
concise product backlog items
Understanding long-term product planning in an
empirical environment
Understanding and practicing agility and,

Scrum Master & Development Team

Coaching the development team in self-organization
and cross-functionality
Teaching and leading the development team to create
high-value products
Removing impediments to the development teams
progress
Facilitating Scrum events as requested or needed and,
Coaching the development team in organizational
environments in which Scrum is not yet fully adopted
and understood.

Scrum Master & Organization

Leading and coaching the organization in its Scrum
adoption
Planning Scrum implementations within the
organization
Helping employees and stakeholders understand and
enact Scrum and empirical product development
Causing change that increases the productivity of the
Scrum Team; and
Working with other Scrum masters to increase the
effectiveness of the application of Scrum in the

Development Team

Generates value for the customer, building high quality

product increments
Self-organizing, self-managing
Negotiates commitments with the product owner
Intensely collaborative
Develops the product
Cross-functional
Organizes work
Reports progress
Continuously improves

Scrum Events/Ceremonies

Sprint planning
Daily Scrum
Sprint review
Sprint retrospective

Sprint Planning
The purpose of the sprint planning meeting is for
the team to commit to the completion of a set of
highest-ranked product backlog items.
These commitments define the sprint backlog
These commitments are commonly referred to as
user stories

Sprint Planning Steps

1. Determine capacity (number of ideal hours in a sprint,
days each team member available, and percentage of time
each member commit).
2. Product owner describe the backlog item.
3. The team determines completion task for that item.
4. Team members volunteer to own the task.
5. Task owners estimate the ideal hours they need to finish
their task.
6. Planning continues until the team reaches capacity.

Daily Scrum

The daily stand-up is for and about the team and its commitments. In
this meeting, the team checks in on how their work is progressing in
the sprint, adjusts plans and gets assistance with removing
impediments.
Every day, same time, same place, same people. This provides a regular
rhythm and cadence on everyones calendar. The meeting last no more
than 15 minutes.

Each team member addresses three questions:

1. What has been accomplished since the last meeting?
2. What will be done before the next meeting?
3. What obstacles are in the way?

Sprint Review
Held at the end of sprint to inspect the increment and adapt the product backlog
if needed
Scrum team and stakeholder collaborate and review what was done in the sprint
Elicit feedback

The purpose of sprint review is :

Team to demonstrate the progress
True-up, compare what was committed by the team and what was delivered
Show and tell
Get direct feedback
Ask help
Share insight

Sprint Retrospective
The sprint retrospective occurs after the sprint review and prior to the next
sprint planning meeting
This is a three-hour time-boxed meeting for one-month sprints. Proportionately
less time is allocated for shorter Sprints
The purpose of the sprint retrospective is to:
Inspect how the last sprint went with regards to people, relationships, process,
and tools
Identify and order the major items that went well and potential improvements
and,
Create a plan for implementing improvements to the way the Scrum team does
its work

Scrum Events
Iteration 1
2 Weeks

Backlog
Creation

Iteratio
n1
Plannin
Backlog
g
Refineme
nt

Iteration 2
2 Weeks
Iteratio
n1
Review
Retrospec
tive 1

Iteration
2
Planning
Backlog
Refineme
nt

Daily Stand-up
Release
Plannin
g

Release
Plannin
g

Iteratio
n2
Review
Retrospec
tive 2

Relea
se

Scrum Artifacts

Product Backlog

Sprint Backlog

Increment

Product Backlog
Higher
Priority

Lower
Priority

Product Backlog

Sprint Backlog

Product Backlog

Sprint Backlog

Product Increment