Lesson 2: Scrum !!!!

Saket Bansal
PMP, PMI-ACP , CSM , ITIL V3 F
www.izenbridge.com

Empirical Process
Scrum
Scrum Roles
Scrum Ceremonies
Scrum Artifacts

www.izenbridge.com

The empirical model of process control provides and

exercises control through frequent inspection and
adaptation for processes that are imperfectly
defined and generate unpredictable and unrepeatable
outputs

www.izenbridge.com

Laying out a process

that repeatable will
produce acceptable
quality output is
called defined
process control.

www.izenbridge.com

Adopt the defined Modeling

approach when the
underlying mechanisms
are reasonably well
understood.

Defined process gives cost

advantage where product
can be priced as commodity

Adopt Empirical process

when the process is too
complicated for the defined
approach

If the commodity produced

is of unacceptable quality ,
rework is high , higher costs
of empirical process control
is the only option

www.izenbridge.com

Requirement Complexity

Technology Complexity

www.izenbridge.com

Empiricism asserts that knowledge comes from experience

and making decisions based on what is known.
Three pillars uphold every implementation of empirical
process control:
Transparency
Inspection
Adaptation

www.izenbridge.com

Empirical Process
Scrum
Scrum Roles
Scrum Ceremonies
Scrum Artifacts

www.izenbridge.com

Scrum in 100 words

Scrum is an agile process that allows us to focus on

delivering the highest business value in the shortest time.

It allows us to rapidly and repeatedly inspect actual working
software.
The business sets the priorities. Teams self-organize to
determine the best way to deliver the highest priority
features.
Every two weeks to a month anyone can see real working
software and decide to release it as is or continue to enhance
it for another sprint.

www.izenbridge.com

Self-organizing teams

Product progresses in a series of month-long sprints

Requirements are captured as items in a list of product

backlog

No specific engineering practices prescribed

One of the agile processes

www.izenbridge.com

10

24 hours

Sprint
30 Days

Sprint goal
Return

Return
Cancel

Sprint backlog

Potentially shippable
product increment

Gift
wrap
Coupons
Cancel
Gift
wrap

Coupons

Product
backlog

www.izenbridge.com

11

Scrum projects make

progress in a series of
sprints
Analogous to Extreme
Programming iterations
Typical duration is a calendar
month at most
A constant duration leads to
a better rhythm
Product is designed, coded,
and tested during the sprint

Sprint
30 Days

www.izenbridge.com

12

Requirements

Design

Code

Test

Rather than doing all of one thing at a

time...
...Scrum teams do a little of everything
all the time

Source: The New New Product Development Game by Takeuchi and

Nonaka. Harvard Business Review, January 1986.
www.izenbridge.com

13

Roles

Product Owner
Scrum Master
Team

Ceremonies

Sprint review
Sprint planning
Sprint retrospective
Daily scrum meeting
Artifacts

Product backlog
Sprint backlog
Increment
www.izenbridge.com

14

Recapitulation

www.izenbridge.com

15

Process of making Burger at fast food

center is?
Defined process as it produces burger of
acceptable quality repeatedly
Does Scrum recommends specific
engineering practice
No, but usually scrum team use some
of the XP practices
Is the Scrum Master is the same like
Project manager
No, next section will talk about it
further

www.izenbridge.com

16

Is it ok to run some of the sprints just

for capturing requirements
No, Its is not recommended as we do
little of everything all the time
Is the scrum duration fixed for 30
calendar days
No, Its is recommended to have one
month or less
Is the sprint and Iterations are the
same ?
Yes, its a timeboxed event of one
month or less

www.izenbridge.com

17

Empirical Process
Scrum
Scrum Roles
Scrum Ceremonies
Scrum Artifacts

www.izenbridge.com

18

Roles

Product Owner
Scrum Master
Team

Ceremonies

Sprint planning
Sprint review
Sprint retrospective
Daily scrum meeting
Artifacts

Product backlog
Sprint backlog
Increment
www.izenbridge.com

19

Define the features of the product

Decide on release date and content
Be responsible for the profitability of the
product (ROI)
Prioritize features according to market
value
Adjust features and priority every iteration,
as needed
Accept or reject work results

www.izenbridge.com

20

Represents management to the project

Responsible for enacting Scrum values and

practices

Removes impediments

Ensure that the team is fully functional

and productive

Enable close cooperation across all roles

and functions

Shield the team from external interferences

www.izenbridge.com

21

Typically 5-9 people

Cross-functional:
Programmers, testers, user experience
designers, etc.

Members should be full-time

May be exceptions (e.g., database
administrator)

www.izenbridge.com

22

Teams are self-organizing

Ideally, no titles but rarely a possibility

Membership should change only between

sprints

www.izenbridge.com

23

Empirical Process
Scrum
Scrum Roles
Scrum Ceremonies
Scrum Artifacts

www.izenbridge.com

24

Roles

Product owner
Scrum Master
Team

Ceremonies

Sprint planning
Daily scrum meeting
Sprint review
Sprint retrospective

Artifacts

Product backlog
Sprint backlog
Increment
www.izenbridge.com

25

Planning
Sprint
Planning
Sprint
Retrospect
ive
Process
Check Act

Sprint
Review /
Product
Check Act

Sprint /
Doing

Daily
Standup
/Collabor
ation and
Coordinati
on

www.izenbridge.com

26

Sprint Planning

www.izenbridge.com

27

The Team and the Product Owner collaborate to help the

Team determine how much Product Backlog it can turn into
functionality during the upcoming Sprint.
The Team create plans (Sprint Backlog) by identifying tasks
for converting selected Product Backlog into functionality

www.izenbridge.com

28

Sprint planning meeting

Team
capacity

Sprint prioritization

Product
backlog

Business
conditions

Analyze and evaluate product

backlog
Select sprint goal

Sprint planning

Current
product

Sprint
goal

Decide how to achieve sprint goal

(design)
Create sprint backlog (tasks)
from product backlog items (user
stories / features)
Estimate sprint backlog in hours

Sprint
backlog

Technology

www.izenbridge.com

29

Prioritized
Product
Backlog

Sprint
Backlog

Facilitate

www.izenbridge.com

30

Team selects items from the product backlog they

can commit to completing

Sprint backlog is created

Tasks are identified and each is estimated (1-16
hours)

Collaboratively, not done alone by the Scrum

Master

High-level design is considered

As a vacation
planner, I want to
see photos of the
hotels.

Code the middle tier (8 hours)

Code the user interface (4)
Write test fixtures (4)
Code the foo class (6)
Update performance tests (4)

www.izenbridge.com

31

The Daily Scrum

Meeting

www.izenbridge.com

32

Fine-grain coordination
Daily commitment
Raising impediments
Peer pressure
Access Progress towards sprint goal

www.izenbridge.com

33

Parameters

Daily
15-minutes
Stand-up

Not for problem solving

Only team members, Scrum
Master, Product Owner, can
talk

Helps avoid other unnecessary

meetings

Team is responsible of
conducting this meeting

www.izenbridge.com

34

Observe

Facilitate

What did you do yesterday?

What will you do today?

Is anything in your way?

These are not status

for the Scrum Master
They are
commitments in
front of peers

www.izenbridge.com

35

Sprint Review

www.izenbridge.com

36

Team presents what it accomplished

during the sprint

Typically takes the form of a demo

of new features or underlying
architecture

Informal
2-hour prep time rule
No slides

Whole team participates

Invite the world

www.izenbridge.com

37

Feedback
on Product

Demo

Feedback
on Product
Facilitate

www.izenbridge.com

38

Sprint
Retrospective

www.izenbridge.com

39

Periodically take a look at what is and is not working

Done after every sprint

Participants
Scrum Master

Team
Product owner (Optional)

www.izenbridge.com

40

Observe

Start doing
Stop doing
Continue doing

Facilitate
This is just one
of many ways
to do a sprint
retrospective

www.izenbridge.com

41

Recapitulation

www.izenbridge.com

42

Sprint Start with which ceremony?

Sprint Planning Meeting
Sprint Ends with which ceremony?
Sprint Retrospective
Which scrum ceremony happens every
day?

Daily Scrum
Which scrum ceremony stakeholders
are allowed to speak?
Sprint Review

www.izenbridge.com

43

Who represent management to scrum

team?
Scrum Master
Who is responsible for identifying task
and assigning to team member?
Team
Who facilitate the sprint retrospective?

Scrum Master
Who Prioritize the product backlog?
Product Owner

www.izenbridge.com

44

Empirical Process
Scrum
Scrum Roles
Scrum Ceremonies
Scrum Artifacts

www.izenbridge.com

45

Roles

Product owner
ScrumMaster
Team

Ceremonies

Sprint planning
Sprint review
Sprint retrospective
Daily scrum meeting
Artifacts

Product backlog
Sprint backlog
Increment
www.izenbridge.com

46

Sprint
Backlog

Increment

Product
Backlog

www.izenbridge.com

47

Product Backlog

www.izenbridge.com

48

The requirements

A list of all desired work (Product Backlog Item) on the

project

Ideally expressed such that each item has value to the users
or customers of the product

Prioritized by the product owner

Reprioritized at the start of each sprint

www.izenbridge.com

49

Sprint
Review

Team
Input

PO
Research

Product Backlog

Sprint Planning

Sprint
Backlog

www.izenbridge.com

50

Good product backlogs should be DEEP (Coined by Roman

Pichler and Mike)
Detailed appropriately
Emergent
Estimated
Prioritized

www.izenbridge.com

51

PBI Type

Example

Feature

As a job seeker I want to search job using

keywords so that I can find the suitable job

Change

As a job seeker I want default ordering od job

search results to be by freshness rather than
location so that its easier to see latest jobs
first

Defects

Fix defect #245 so that special character in

search wont crash the system

Technical Improvement Move to the latest version of Internet Explorer

Knowledge Acquisition

Create prototype using two databases (RDMS

and NO SQL) and run performance test to
determine which would be better approach for
our system.

www.izenbridge.com

52

Backlog Item

Estimate

Allow a guest to make a reservation

As a guest, I want to cancel a reservation.

As a guest, I want to change the dates of a

reservation.

As a hotel employee, I can run RevPAR reports

(revenue-per-available-room)

Improve exception handling

...

30

...

50

www.izenbridge.com

53

Sprint Backlog

www.izenbridge.com

54

The Sprint Backlog defines the work the Team will perform to
turn Selected Product Backlog items into a Done Increment.
The list emerges during the Sprint.
Each ongoing task identifies those responsible for doing the
work
Each Tasks has information about estimated amount of work
remaining on the task on any given day during the Sprint.

www.izenbridge.com

55

A short statement of what the work will be focused on during

the sprint
Life Sciences
Database Application
Make the application run on
SQL Server in addition to
Oracle.

Support features necessary for

population genetics studies.

Financial services
Support more technical
indicators than company ABC
with real-time, streaming data.
www.izenbridge.com

56

Individuals sign up for work of their own choosing

Work is never assigned

Estimated work remaining is updated daily

Any team member can add, delete or change the sprint

backlog

Work for the sprint emerges

If work is unclear, define a sprint backlog item with a larger

amount of time and break it down later

Update work remaining as more becomes known

www.izenbridge.com

57

Sprint
Planning

Sprint Backlog

Maintain

During the
Day

Daily
Scrum

www.izenbridge.com

58

Increment

www.izenbridge.com

59

The Increment is the sum of all the Product Backlog items

completed during a Sprint and all previous Sprints.
At the end of a Sprint, the new Increment must be Done,
It must be in useable condition (Potentially shippable
product)

www.izenbridge.com

60

Everyone must understand what done means

This varies significantly per Scrum Team, members must
have a shared understanding of what it means for work to be
complete, to ensure transparency
This guides Development Team in knowing how many
Product Backlog items it can select during a Sprint Planning
Meeting.
The purpose of each Sprint is to deliver Increments of
potentially releasable functionality that adhere to Definition
of Done.
Definition of Done may change during the project

www.izenbridge.com

61

Demo
Increment

Develop
Increment

www.izenbridge.com

62

Recapitulation

www.izenbridge.com

63

Product Backlog is Input to which

scrum meeting?
Sprint Planning Meeting
What is the output of sprint planning
meeting?
Sprint Backlog
Team member can add / delete /
change items in which backlog?

Sprint Backlog
What defines that functionality is
done?
Definition of Done

www.izenbridge.com

64

At the end of sprint team delivers ..

Increment of Potentially Shippable
Product Functionality
Who creates Sprint backlog
Team
What get demoed in Sprint Review
Meeting

Increment
Product Owner usages which artifact to
manage requirement?
Product Backlog

www.izenbridge.com

65

Empirical Process
Scrum
Scrum Roles
Scrum Ceremonies
Scrum Artifacts

www.izenbridge.com

66

This

Presentation includes extract from Mike Cohns

Presentation www.mountaingoatsoftware.com
Includes Reference from Scrum Guide (www.scrum.org)
Book : Agile Project Management with Scrum : Ken
Schwaber

www.izenbridge.com

67

Hope You have found

Presentation
comprehensible! Drop
us a note for any query.

www.izenbridge.com

68