Introduction to Scrum

(Most popular agile framework)

 What is SCRUM ?

• Scrum is a lightweight framework that helps people, teams

and organizations generate value through adaptive solutions
for complex problems

• Scrum is the most popular agile framework

• Initially it was focused on Software Development only

 SCRUM is an agile framework

Popular Agile Frameworks:

Scrum
eXtreme Programming (XP)
Feature Driven Development (FDD)
Adaptive Software Development (ASD)
Lean
KANBAN
Disciplined Agile (DA)
Scaled Agile Framework (SAFe)
SCRUM is all about doing agile

• SCRUM helps to apply agile

values and principle

• Its all about implementing

agile in projects and
operation
 SCRUM basics

• Scrum is founded on empiricism

and lean thinking

• Scrum employs an iterative,

incremental approach to optimize
predictability and to control risk

• Scrum is simple to understand,

difficult to master
 3 SCRUM Pillars

Transparency Inspection Adaptation

Work must be Goals must be The adjustment

visible to those inspected frequently must be made as
performing the and diligently to soon as possible
work & receiving detect potentially to minimize
the work undesirable variances further deviation.
 SCRUM : Five Values

Commitment

Courage Focus

SCRUM
VALUES

Respect Openness
 History

The term is borrowed from rugby,

Jeff Sutherland, Ken Schwaber
where a scrum is a formation of players

• 1995: Introduced “The Scrum Development process” paper

• 2001: Introduced “Agile Manifesto” guide

• 2002: Formed “Scrum Alliance” organization

 SCRUM Framework

2-4 Weeks

Product Increment

• Entire product is split into no of increments/features

• Whole project is divided into several sprints
• Follow incremental and iterative method
 SCRUM Framework(3-4-3)

3 Roles/ SCRUM Team 4 Events/ Ceremonies 3 Artifacts

Scrum Master Sprint Planning Product Backlog

Product Owner Daily Scrum Sprint Backlog

Development Team Sprint Review Product Increment

Sprint Retrospective
 SPRINT
• The heart of Scrum is a Sprint

• A time-box of 1 month or less during which a ‘Done’,

useable and potentially releasable product Increment is
created
 SPRINT
• Sprint 0 : Often used for team formation and initial product
backlog generation

• Sprint 1: Actual development begins

• Spike: A test/pilot sprint to check feasibility/do analysis(a spike is

a story that cannot be estimated until a development team runs
investigation)

Sprint Sprint Sprint Sprint Sprint Sprint

- - - -
0 1 2 3 4 5
 Scrum Events(4)
Events performed during a sprint

[15 Minutes]
[Max 4 Hrs for 1 [Max 3 Hrs for 1
[Max 8 Hrs for 1 Month Sprint] Month Sprint]
Month Sprint]

Development
Work
 Scrum Events: Sprint Planning

Sprint1

 Sprint Planning initiates the Sprint by laying out the work to be

performed for the Sprint

 This resulting plan is created by the collaborative work of the

entire Scrum Team
 Scrum Events: Sprint Planning

Sprint Planning answers the following:

• What can be delivered in the Increment resulting from the

upcoming Sprint?

• How the work will be delivered for the Increment to be achieved?

 Scrum Events: Daily Scrum

 The purpose of the Daily Scrum is to inspect progress toward the

Sprint Goal

 The Daily Scrum is a 15-minute event for the Developers of the

Scrum Team
 Scrum Events: Daily Scrum

• What did I do yesterday that helped the Development Team

meet the Sprint Goal?

• What will I do today to help the Development Team meet the

Sprint Goal?

• Do I see any impediment that prevents me or the Development

Team from meeting the Sprint Goal?
 Scrum Events: Sprint Review

 The purpose of the Sprint Review is to inspect the outcome of

the Sprint

 The Sprint Review is the second to last event of the Sprint

 The Scrum Team presents the results of their work to key

stakeholders
 Scrum Events: Sprint Review
The Sprint Review includes the following elements:

• Attendees include the Scrum Team and key stakeholders invited

by the Product Owner

• The Product Owner explains what Product Backlog items have

been “Done” and what has not been “Done”

• The Development Team demonstrates the work that it has

“Done” and answers questions about the Increment
 Scrum Events: Sprint Retrospective

 The purpose of the Sprint Retrospective is to plan ways to

increase quality and effectiveness

 The Sprint Retrospective concludes the Sprint

 It is time boxed to a maximum of three hours for a one-month

Sprint
 Scrum Events: Sprint Retrospective

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;

• Create a plan for implementing improvements to the way the

Scrum Team does its work.
 Scrum Events
Sprint
Retro
Sprint
Planning Daily Scrum
Sprint
Review

Sprint1

Day 0 Day 30
 Scrum Roles(3)

Development Team

• The Scrum Team is small enough to remain nimble

• Large enough to complete significant work within a Sprint
• Typically 5-12 people
• No sub-teams or hierarchies
 Scrum Roles : Product Owner

• Solely responsible for managing product backlog

• The Product Owner is one person, not a committee

 Scrum Roles : Product Owner

Product Owners responsibilities include:

• Clearly expressing Product Backlog items

• Ordering the items in the Product Backlog to best achieve goals and missions
•
• Optimizing the value of the work the Development Team performs

• Ensuring that the Product Backlog is visible, transparent, and clear to all

• Ensuring the Development Team understands items in the Product Backlog

 Scrum Roles : Scrum Master

 Is a servant leader for the Scrum Team

 Teaches and promotes Scrum to Team & Org.

 Removes Impediments & Protects DT from distraction

 Scrum Roles : Scrum Master

Scrum Master Service to the Product Owner :

• Ensuring that goals, scope, and product domain are understood

by everyone

• Finding techniques for effective Product Backlog management

• Understanding and practicing agility

• Facilitating Scrum events as requested or needed

 Scrum Roles : Scrum Master

Scrum Master Service to the Development Team

• Coaching the Development Team in self-organization and cross-

functionality

• Helping the Development Team to create high-value products

• Removing impediments to the Development Team’s progress

• Facilitating Scrum events as requested or needed

 Scrum Roles : Development Team

 Responsible to work & deliver releasable Increments

 Self-organizing: team decide what and how to deliver

 Cross-functional: team should have all required skills

 Scrum Artifacts(3)

What to do What to do now

(overall)? i.e. in current
sprint? What has been
“Done”?
 Scrum Artifacts : Product Backlog

 Product Backlog is an emergent, ordered list of what is

needed in the product
 It is the single source of work undertaken by the Scrum Team
 Owned by Product Owner
 Scrum Artifacts : Product Backlog

Backlog Refinement:
• Product Backlog refinement is the act of breaking down and further defining
Product Backlog items into smaller more precise items.

• This is an ongoing activity to add details, such as a description, order, and size.
Attributes often vary with the domain of work.
 Scrum Artifacts : Product Backlog

Definition of Done:
• The Definition of Done is a formal description of the state of the Increment when it
meets the quality measures required for the product

• The moment a Product Backlog item meets the Definition of Done, an Increment is
born.
 Scrum Artifacts : Product Backlog

Definition of Ready
• A Definition of Ready means that stories must be immediately actionable

• The Definition of Ready is a set of agreements that lets everyone know when
something is ready to begin, e.g., when a user story is ready to be taken into a
sprint.
 Scrum Artifacts : Sprint Backlog

 The Sprint Backlog is composed of the set of Product

Backlog items selected for the Sprint

 It is a highly visible, real-time picture of the work that the

Developers plan to accomplish during the Sprint
 Scrum Artifacts: Product Increment

 An Increment is a concrete stepping stone toward the

Product Goal

 Multiple Increments may be created within a Sprint

 Product owner takes decision about release of increment