Life Cycle Models:

Scrum

1
 Practice Questions
• What are the stages of iterative waterfall
model?
• What are the disadvantages of the iterative
waterfall model?
• Why has agile model become so popular?
• What difficulties might be faced if no life cycle
model is followed for a certain large project?

2
 Suggest Suitable Life Cycle Model
• A software for an academic institution to automate
its:
– Course registration and grading
– Fee collection
– Staff salary
– Purchase and store inventory
• The software would be developed by tailoring a
similar software that was developed for another
educational institution:
– 70% reuse
– 10% new code and 20% modification
3
 Practice Questions
• Which types of risks can be better handled using
the spiral model compared to the prototyping
model?
• Which type of process model is suitable for the
following projects:
– A customization software
– A payroll software for contract employees that
would be add on to an existing payroll software

4
 Practice Questions
• Which lifecycle model would you select for the
following project which has been awarded to us by
a mobile phone vendor:
– A new mobile operating system by upgrading the
existing operating system
– Needs to work well efficiently with 4G systems
– Power usage minimization
– Directly upload backup data on a cloud infrastructure
maintained by the mobile phone vendor
5
Scrum

6
 Scrum: Characteristics
• Self-organizing teams

• Product progresses in a series of month-

long sprints

• Requirements are captured as items in a

list of product backlog

• One of the agile processes

7
 Daily
Scru
m
Sprint Sprint
planning review

Scrum
Sprint
Product backlog backlog Product
increment

8
 Sprint
• Scrum projects progress in a series of
“sprints”
– Analogous to XP iterations or time boxes
– Target duration is one month

• Software increment is designed, coded,

and tested during the sprint
• No changes entertained during a sprint
9
 Scrum Framework
• Roles : Product Owner, Scrum Master, Team

• Ceremonies : Sprint Planning, Sprint

Review, Sprint Retrospective, and Daily
Scrum Meeting
• Artifacts : Product Backlog, Sprint Backlog,
and Burndown Chart
10
 Key Roles and Responsibilities in a Scrum Team
• Product Owner
– Represents customers’ views and interests.
• Development Team
– Team of five-nine people with cross-functional
skill sets.
• Scrum Master (aka Project Manager)
– Facilitates scrum process and resolves
impediments at the team and organization level
by acting as a buffer between the team and
outside interference. 11
 Product Owner
• Defines the features of the product
• Decides on release date and content
• Prioritizes features according to usefullness
• Adjusts features and priority every
iteration, as needed
• Accepts or reject work results.
12
 The Scrum Master
• Represents management in the project
• Removes impediments
• Ensures that the team is fully functional and
productive
• Enables close cooperation across all roles and
functions
• Shields the team from external interferences
13
 Scrum Team
• Typically 5-10 people
• Cross-functional
– QA, Programmers, UI Designers, etc.

• Teams are self-organizing

• Membership can change only
between sprints 14
 Sprint
• Fundamental process flow of Scrum
• It is usually a month-long iteration:
– during this time an incremental product
functionality completed
• NO outside influence allowed to interfere
with the Scrum team during the Sprint
• Each day begins with the Daily Scrum
Meeting 15
 Ceremonies
• Sprint Planning Meeting

• Daily Scrum

• Sprint Review Meeting

16
 Sprint Planning
• Goal is to produce Sprint Backlog
• Product owner works with the Team to
negotiate what Backlog Items

• Scrum Master ensures Team agrees to

realistic goals

17
• Daily Daily Scrum
• 15-minutes
• Stand-up meeting
• Not for problem solving
• Three questions:
1. What did you do yesterday
2. What will you do today?
3. What obstacles are in your way?
18
 Daily Scrum
• Is NOT a problem solving session

• Is NOT a way to collect information about WHO is

behind the schedule

• Is a meeting in which team members review what is

done and make informal commitments to each
other and to the Scrum Master

• Is a good way for a Scrum Master to track the

progress of the Team 19
• Team presents what it accomplished during
the sprint
• Typically takes the form of a demo of new
features
• Informal Sprint Review
– 2-hour prep time rule Meeting
• Participants
– Customers
– Management
– Product Owner
– Other team members 20
 Product Backlog
• A list of all desired work on the project

– Usually a combination of

• story-based work (“let user search and replace”)

• task-based work (“improve exception handling”)

• List is prioritized by the Product Owner

– Typically a Product Manager, Marketing,

Internal Customer, etc.
21
 Product Backlog

• Requirements for a system, expressed as a

prioritized list of Backlog Items

– Managed and owned by Product Owner

– Spreadsheet (typically)

22
Sample Product Backlog

23
 Sprint Backlog
• A subset of Product Backlog Items,
which define the work for a Sprint

– Created by Team members

– Each Item has it’s own status

– Updated daily
24
 Sprint Backlog during the Sprint

• Changes occur:
– Team adds new tasks whenever they need to in
order to meet the Sprint Goal
– Team can remove unnecessary tasks
– But: Sprint Backlog can only be updated by the
team

• Estimates are updated whenever there’s

new information 25
 Burn down Charts
• Are used to represent “work done”.
• Are remarkably simple but effective Information
disseminators
• 3 Types:
– Sprint Burn down Chart (progress of the Sprint)

– Release Burn down Chart (progress of release)

– Product Burn down chart (progress of the Product)

26
 Sprint Burn down Chart

• Depicts the total Sprint Backlog hours remaining

per day
• Shows the estimated amount of time to
complete
• Ideally should burn down to zero to the end of
the Sprint
• Actually is not a straight line
27
Sprint Burndown Chart

28
 Release Burndown Chart
• Will the release be done
on right time?

• How many more sprints?

• X-axis: sprints

• Y-axis: amount of story

points remaining 29
 Product Burndown Chart

• Is a “big picture” view of project’s progress

(all the releases)

Actual
burndown
Story
points
Expected
burndown

Sprint

30
 Scalability of Scrum

• A typical Scrum team is 6-10 people

• Jeff Sutherland - up to over 800

people

• "Scrum of Scrums" or "Meta-

Scrum“
31
Thank You!!