UNIT - II

SCRUM
G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

OVERVIEW

 Classification of Scrum.

 Work products, roles, and practices.

 Common mistakes, adoption and process mixtures,

strengths and weaknesses.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
 Scrum's unique importance among the methods

IS its strong promotion of self-directed teams

 Daily team measurement

 Avoidance of prescriptive process

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Some key practices include:

self-directed and self-organizing team

no external addition of work to an iteration, once chosen

daily stand-up meeting with special questions

usually 30-calendar day iterations

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
 Demo to external stakeholders at end of each iteration

 each iteration, client-driven adaptive planning

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Method Overview - Classification

In terms of cycles and ceremony Scrum is uniquely precise

on the length of iterations

usually30 calendar days, a more-or-less common length

compared to other IID methods.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
 In terms of scope on the Cockburn scale, Scrum covers the
cells

 Althoughone Scrum team should be seven or less, multiple

teams may form a project

 Ithas been used on both small projects and those involving

hundreds of developers.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
 Scrum practices include working in a common project
room, it scales via a "scrum of scrums" where small teams
work together and hold a daily stand-up meeting

 Representatives from each those teams likewise meet daily.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Introduction

Scrum – definition [SB02]

 Is an IID method that emphasizes a set of project

management values and practices, rather than those in
requirements, implementation, and so on

A key Scrum theme is its emphasis on empirical rather than

defined process
G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Lifecycle

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
The Scrum lifecycle is composed of four phases:

 Planning

 Staging

 Development

 Release.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Work products, Roles, and
Practices

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Roles

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Practices

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Core Practices

Pre-game planning and staging :

During Pre-game Planning, all stakeholders can contribute

to creating a list of features, use cases, enhancements, defects,
and so forth, recorded in the Product Backlog.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
 One Product Owner is designated its owner, and requests
are mediated through her

 During this session, at least enough work for the first

iteration is generated, and likely much more

 Starting at these meeting and evolving over time, is

identification of the Release Backlog

 The subset of the Product Backlog that will make the next
operational or product release.G.SENTHIL KUMAR Asst.Prof
Dept.of Software Engineering
SRM UNIVERSITY
Sprint planning

Before the start of each iteration—or Sprint—two

consecutive meetings are held.

Inthe first, stakeholders meet to refine and re-prioritize the

Product Backlog and Release Backlog

choose goals for the next iteration

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
 In the second meeting, the Scrum Team and Product Owner
meet to consider how to achieve the requests

 and to create a Sprint Backlog of tasks (in the 4–16 hour

range) to meet the goals

 Ifestimated effort exceeds resources, another planning

cycle occurs.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
 As the iteration proceeds, the Sprint Backlog is updated,
often daily during the early part of the iteration, as new
tasks are discovered

 As a history of many Sprint Backlogs grows, the team

improves their creation of new ones

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Sprint

Work is usually organized in 30-calendar-day

iterations; each is called a Sprint

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Self-directed and self-organizing
teams
During an iteration, management and the Scrum Master do
not guide the team in how to fulfill the iteration goals, solve
its problems nor plan the order of work

The team is empowered with the authority and

resources to find their own way, and solve their own
problems

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
 This hands-off approach for 30 days, except to provide

resources and remove blocks

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Scrum meeting

Each workday at the same time and place, hold a meeting

with the team members in a circle

the same special Scrum questions are answered by each

team member
G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Don't add to iteration

During an iteration, management does not add work to the

team or individuals.

Uninterrupted focus is maintained

In the rare case something has to be added ,some thing else
should ideally be removed.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
 But, before each new iteration, the Product Owner and
Management have the right and responsibility to re-
prioritize the Product Backlog

 indicate what to do in the next iteration as long as the work

request estimates don't exceed the resources.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Scrum master firewall

The Scrum Master looks out to ensure the team is not

interrupted by work requests from other external parties

If they occur, removes them and deals with all political and
external management issues

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
 The Scrum Master also works to ensure Scrum is
applied, removes reported blocks, provides resources,
and makes decisions when requested

 She also has to take initiative when she sees during the
meeting that someone isn't completing work, if the team
doesn't speak up.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Decision in one hour

Blocks reported at the Scrum Meeting that require

decisions by the Scrum Master are ideally decided
immediately, or within one hour

The value of "bad decisions are better than no decisions,

and they can be reversed" is promoted

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Blocks gone in one day :

Blocks reported at the Scrum Meeting are ideally removed

before the next meeting.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Chickens and pigs :
During the Scrum Meeting, only the Scrum Team can talk
(the pigs).

Anyone else can attend, but should remain silent (the

chickens), even the CEO.

An exception is management (e.g., CEO) feedback on

survival points or explanation of the business relevance of the
team's work
G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
 The Scrum needs to be a vehicle for communicating the

product vision and organization goals

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Teams of seven

Scrum can scale to large projects, but recommends one

team have a maximum of seven members.

Larger projects are multi-team.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Common room

Ideally, the team work together in a common project room,

rather than separate offices or cubes

Separate, private space is still available for other activities

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
 However, teams composed of geographically spread
members, participating by speakerphone in the Daily
Scrum, have reported success

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Daily build

At least one daily integration and regression test across

all checked-in code for the project

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Sprint review

At the end of each iteration, there is a review meeting

(maximum of four hours) hosted by the Scrum Master

The team, Product Owner, and other stakeholders attend.

There is a demo of the product

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
 Goals include informing stakeholders of the system
functions, design, strengths, weaknesses, effort of the team,
and future trouble spots.

 Feedback and brainstorming on future directions is

encouraged, but no commitments are made during the
meeting
G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
 Later at the next Sprint Planning meeting, stakeholders and
the team make commitments.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
The Scrum Meeting: Details

The Scrum Meeting—or scrum—is the heartbeat of Scrum

and the project

Each workday at the same time and place, hold a

meeting with the team members

standing in a circle, at which time the same special

questions are answered by each member

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
What will you do between now and the next Scrum?

What is getting in the way (blocks) of meeting the iteration goals

What have you done since the last Scrum

Any tasks to add to the Sprint Backlog? (missed tasks, not new
requirements)

Have you learned or decided anything new, of relevance to some of the

team members? (technical, requirements, …)

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Other points:

The meeting is ideally held in a stand-up circle

On average, 15 or 20 minutes for 7–10 people. Longer meetings are

common near the start of an iteration.

Non-team members (chickens) are outside the circle.

It is held next to a whiteboard at which all the tasks and blocks are
written when reported

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
The Scrum Master erases blocks only once they've been removed.

There is a speaker-phone for offsite member participation—which is

required.

The Scrum Master ensures the rules are followed and prepares the
location for an efficient meeting.

Must start on time. Late fines collected by the Scrum Master and
donated to charity are a popular rule.
G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
 Chickens and Pigs rule enforced: Non-team members don't talk or
ask questions

 The Scrum needs to be a vehicle for communicating the product vision

and organization goals.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
No other discussion is allowed beyond the three (or five) questions.

The Scrum Master has authority to refocus the discussion

If other issues need discussion, secondary meetings immediately after

the Scrum Meeting occur, usually with subsets of the team.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
The Value of the Scrum Meeting
 The Scrum Meeting creates the daily mechanism to quickly
inform the team about the state of the project and people.

 External people can observe the daily Scrums to get an accurate,

timely, and information-rich measure of progress and issues

 It supports openness and allows resolution of dependencies and

conflicts in real time to maximize throughput.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
 VALUE : When a person reports on what they are doing
for the next day, they are expressing a kind of social promise
to the team.

This increases responsibility and follow-through.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Value: Scrum is based on the insight that software development is
creative and unpredictable new product development

Therefore empirical rather than defined methods are needed

The Scrum Meeting provides the frequent measuring and adaptive

response mechanism that empirical methods require.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Value: It is important to have people (and teams) that are continuously
improving and learning

Value: Shared language, values, and practices help a development team.

This is created and reinforced in the daily Scrum.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Work products

Scrum allows any other work products of value to the project.

 For example, it can be combined with some UP practices, and one can
create a Vision or Risk List, using UP terminology.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
 Product Backlog— A sample, partial Product Backlog is
shown

 Note that all conceivable items go in the backlog and are

prioritized by the Product Owner

 The estimates (in person-hours of effort) start as rough

guidelines, refined once the team commits to an item

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Sprint Backlog :

A sample Sprint Backlog is shown in Figure 7.4. Note the

daily estimate of work remaining for each task

these columns also show the date (e.g., 6 of Jan) and total
hours remaining on each day (e.g., Jan 6, 362 hours).

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
 It is updated daily by the responsible members or by a
daily tracker who visits each member.

 New estimates are allowed to increase above the original

estimate.

 The simplest (and thus preferred) tool is a spreadsheet

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Sprint Backlog Graph :

Itis a visual summary of estimated task hours remaining in the

Sprint Backlog.

 In Scrum, this is considered the most critical project data to track.

Recommended: Post an updated version of this each day on the wall by

the Scrum

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Other Practices and Values

Workers daily update the Sprint Backlog

 Once tasks are underway, individuals are responsible for

daily updates

 estimating the time remaining for their tasks.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
 No PERT charts allowed

 A PERT chart is built on the assumption that the tasks of a project can
be identified, ordered, and reliably estimated, that there is minimal
change and noise in the system, and in general that a defined process
can be applied

 This is inconsistent with the recognition in iterative and agile methods

that software is semi-chaotic new product development with high degrees
of change and noise, and defined processes can't apply.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Scrum Master strengthens vision

 She needs to daily share and clarify the overall project

vision

goals of the Sprint, perhaps at the start of the Scrum

meeting.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Replace ineffective Scrum Master

 The manager/Scrum Master is the servant of the

developers, not vice versa.

If Scrum Master is not removing blocks promptly, acting as

a firewall, and providing resources, the Scrum founders
encourage replacing the Scrum Master

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
The Scrum values are described in

Commitment: The Scrum Team commits to a defined goal

for an iteration, and is given the authority and autonomy to
decide themselves how best to meet it

Focus — The Scrum Team has to be able to focus on the

stated goals of the iteration, without distraction

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Openness

The openly accessible Product Backlog makes visible the

work and priorities.

The Daily Scrums make visible the overall and individual

status and commitments.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Common Mistakes and Misunderstandings :

Error: Not a self-directed team; managers or Scrum Master

direct or organize the team

(This is especially true for the Scrum Master during the Scrum Meeting,
when there is a natural tendency for the team to look to a leader for
direction and solutions.)

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
 Error: No daily update of the Sprint Backlog by members
or daily tracker

Error: New work added to iteration or individual

Error: Product Owner isn't involved or doesn't decide

(Scrum is customer driven; the Product Owner needs to
decide what the Product Backlog priorities are and choose the
requirements for the next iteration.)

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Error: No Sprint Review

Error: Many masters

(Scrum requires one voice on the Product Backlog requirements,
priorities, and work for the next iteration: the Product Owner)

Error: Documentation is bad

(Scrum isn't anti-documentation; discussion of project work products is
simply outside the scope of its definition)

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
 Error: Design or diagramming is bad

 Error: Full team (including customers and management)

not briefed in Scrum and its values

 Error: Scrum Meeting too long or unfocused

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Error: Each iteration ends in a production release

Error: Predictive planning; PERT chart planning

Error: Iteration doesn't end in an integrated and tested

partial product

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Sample Projects

Large— IDX Web-enabled benefits suite

 One year, 330 people across multiple related projects, an E300 project on the
Cockburn scale, [SB02]

 A suite of 15 related applications were developed within one year of adopting

Scrum, after three years of struggle to deliver one application.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Medium— Caremark

 Four months, 20 people, an E20 project, [SB02]

After two years of struggle, 160 staff at its height, and no

delivery, Scrum was introduced with a reduced team size of
20 developers (10 new hires).

In four months, a successful production release was created.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Small— Individual Personal News Page

One month, eight people, a C20 project [SB02]

After nine months without delivery, Scrum was adopted,

and a usable production release emerged after one 30-day
iteration

After five months of releases, most of the original goals

were achieved.
G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Process Mixtures

Scrum + Evo

Some Evo practices are compatible with Scrum

Scrum's 30-day iteration length is not consistent with Evo—

too long.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Scrum + UP

The Scrum practices are either equal to or specializations of UP

practices

The Product Backlog is an acceptable portion of the UP Project

Plan

The Sprint Backlog is an acceptable version of the UP Iteration

Plan.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
 One area of different emphasis is the presence in the UP of
optional but predefined activities

 UPdescribes a set of possible activities related to

requirements analysis, testing, and so forth.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Scrum + XP

Most Scrum practices are compatible with XP or refinements,

such as the Scrum Meeting

 The Scrum Backlog and progress tracking approaches are minor

variations of XP practices

And so simple that they are well within the XP spirit of "do the
simplest thing that could possibly work."

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
Strengths

Simple practices and management work products.

Individual and team problem solving and self-management.
Evolutionary and incremental requirements and
development, and adaptive behavior.
Customer participation and steering.

Focus.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY
 Openness and visibility.
 Easily combined with other methods.
 Team communication, learning, and value-building.
 Team building via the daily Scrum, even if not in common
project room.

G.SENTHIL KUMAR Asst.Prof

Dept.of Software Engineering

SRM UNIVERSITY