8/9/22

An Introduction
An Introduction to Scrum
to Scrum
Presented by
<your name here>
<you>
<date> <date>

Mountain Goat Software, LLC Mountain Goat Software, LLC

1 2

We re losing the relay race

Scrum in 100 words

The… relay race approach to product
development…may conflict with the goals of
maximum speed and flexibility. Instead a
holistic or rugby approach—where a team
tries to go the distance as a unit, passing the
ball back and forth—may better serve
today s competitive requirements.
Hirotaka Takeuchi and Ikujiro Nonaka, The New
New Product Development Game , Harvard
Business Review, January 1986.
• 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 (every two weeks to one month).
• 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.

Mountain Goat Software, LLC Mountain Goat Software, LLC

3 4

Scrum origins Scrum has been used by:

• Jeff Sutherland •Microsoft •Intuit
• Initial scrums at Easel Corp in 1993 •Yahoo •Nielsen Media
• IDX and 500+ people doing Scrum
•Google •First American Real Estate
• Ken Schwaber •Electronic Arts •BMC Software
• ADM •High Moon Studios •Ipswitch
• Scrum presented at OOPSLA 95 with •Lockheed Martin •John Deere
Sutherland
• Author of three books on Scrum
•Philips •Lexis Nexis
•Siemens •Sabre
• Mike Beedle
•Nokia •Salesforce.com
• Scrum patterns in PLOPD4
•Capital One •Time Warner
• Ken Schwaber and Mike Cohn •BBC •Turner Broadcasting
• Co-founded Scrum Alliance in 2002, initially
within the Agile Alliance •Intuit •Oce
Mountain Goat Software, LLC Mountain Goat Software, LLC

5 6

1
 8/9/22

Scrum has been used for: Characteristics

•
•
Commercial software • Video game development
• FDA-approved, life-critical systems
• Self-organizing teams
•
In-house development
Contract development • Satellite-control software • Product progresses in a series of month-long
• Fixed-price projects • Websites sprints
• Financial applications • Handheld software • Requirements are captured as items in a list of
• ISO 9001-certified • Mobile phones product backlog
•
applications
Embedded systems
• Network switching applications
• ISV applications
• No specific engineering practices prescribed
• 24x7 systems with 99.999%
uptime requirements
• Some of the largest applications in • Uses generative rules to create an agile
use environment for delivering projects
• the Joint Strike Fighter
• One of the agile processes

Mountain Goat Software, LLC Mountain Goat Software, LLC

7 8

The Agile Manifesto–a statement of

values Project noise level

Individuals and
over Process and tools
interactions Far from
Agreement
Comprehensive Anarchy
Working software over
Requirements

documentation Complex
Co
Customer m
p li
over Contract negotiation
collaboration ca Source: Strategic Management and
te Organizational Dynamics by Ralph Stacey in
d Agile Software Development with Scrum by

Close to Simple
Ken Schwaber and Mike Beedle.

Responding to change over Following a plan Agreement

Far from
Close to
Certainty

Certainty
Technology
Source: www.agilemanifesto.org
Mountain Goat Software, LLC Mountain Goat Software, LLC

9 10

Scrum 24 hours
Putting it all together

Sprint
2-4 weeks
Sprint goal
Return
Sprint Potentially shippable
Return
Cancel backlog product increment
Gift
Coupons
wrap
Gift
Cancel
wrap Coupons
Product
backlog Image available at
www.mountaingoatsoftware.com/scrum
Mountain Goat Software, LLC Mountain Goat Software, LLC

11 12

2
 8/9/22

Sequential vs. overlapping

Sprints development
• Scrum projects make progress in a series of Requirements Design Code Test
sprints
• Analogous to Extreme Programming iterations
• Typical duration is 2–4 weeks or a calendar Rather than doing all of
one thing at a time...
month at most ...Scrum teams do a little
• A constant duration leads to a better rhythm of everything all the time

• Product is designed, coded, and tested during

the sprint
Source: The New New Product Development Game by Takeuchi
and Nonaka. Harvard Business Review, January 1986.
Mountain Goat Software, LLC Mountain Goat Software, LLC

13 14

No changes during a sprint Scrum framework

Roles
•Product owner
Change •ScrumMaster
•Team
Ceremonies
•Sprint planning
•Sprint review
•Sprint retrospective
•Daily scrum meeting
Artifacts
• Plan sprint durations around how long you can •Product backlog
commit to keeping change out of the sprint •Sprint backlog
•Burndown charts
Mountain Goat Software, LLC Mountain Goat Software, LLC

15 16

Scrum framework Product owner

Roles
•Product owner • Define the features of the product
•ScrumMaster
•Team • Decide on release date and content
Ceremonies
•Sprint planning
• Be responsible for the profitability of the
•Sprint review product (ROI)
•Sprint retrospective • Prioritize features according to market value
•Daily scrum meeting
Artifacts
• Adjust features and priority every iteration, as
needed
•Product backlog
•Sprint backlog • Accept or reject work results
•Burndown charts
Mountain Goat Software, LLC Mountain Goat Software, LLC

17 18

3
 8/9/22

The ScrumMaster The team

• Represents management to the project • Typically 5-9 people
• Responsible for enacting Scrum values and • Cross-functional:
practices • Programmers, testers, user experience designers,
• Removes impediments etc.
• Ensure that the team is fully functional and • Members should be full-time
productive • May be exceptions (e.g., database administrator)

• Enable close cooperation across all roles and

functions
• Shield the team from external interferences
Mountain Goat Software, LLC Mountain Goat Software, LLC

19 20

The team Scrum framework

Roles
•Product owner
• Teams are self-organizing •ScrumMaster
•Team
• Ideally, no titles but rarely a possibility
• Membership should change only between sprints
Mountain Goat Software, LLC Mountain Goat Software, LLC
Ceremonies
•Sprint planning
•Sprint review
•Sprint retrospective
•Daily scrum meeting
Artifacts
•Product backlog
•Sprint backlog
•Burndown charts

21 22

Sprint planning
Sprint planning meeting
Team
capacity
• Team selects items from the product backlog they
Sprint prioritization can commit to completing
Product • Analyze and evaluate product Sprint • Sprint backlog is created
backlog backlog goal • Tasks are identified and each is estimated (1-16 hours)
• Select sprint goal
• Collaboratively, not done alone by the ScrumMaster
Business
conditions Sprint planning • High-level design is considered
• Decide how to achieve sprint goal
Current (design)
Sprint As a vacation Code the middle tier (8 hours)
• Create sprint backlog (tasks) from
product
product backlog items (user stories backlog planner, I want to Code the user interface (4)
/ features) see photos of the Write test fixtures (4)
Code the foo class (6)
Technology • Estimate sprint backlog in hours hotels. Update performance tests (4)

Mountain Goat Software, LLC Mountain Goat Software, LLC

23 24

4
 8/9/22

The daily scrum Everyone answers 3 questions

• Parameters 1
What did you do yesterday?
• Daily
• 15-minutes 2
• Stand-up What will you do today?
• Not for problem solving
• Whole world is invited 3
• Only team members, ScrumMaster, product Is anything in your way?
owner, can talk • These are not status for the ScrumMaster
• Helps avoid other unnecessary meetings • They are commitments in front of peers
Mountain Goat Software, LLC Mountain Goat Software, LLC

25 26

The sprint review Sprint retrospective

• Team presents what it accomplished during • Periodically take a look at what is and is not
the sprint working
• Typically takes the form of a demo of new • Typically 15–30 minutes
features or underlying architecture • Done after every sprint
• Informal • Whole team participates
• 2-hour prep time rule • ScrumMaster
• No slides • Product owner
• Whole team participates • Team
• Invite the world • Possibly customers and others
Mountain Goat Software, LLC Mountain Goat Software, LLC

27 28

Start / Stop / Continue Scrum framework

Roles
• Whole team gathers and discusses what •Product owner
they d like to: •ScrumMaster
•Team
Ceremonies
Start doing •Sprint planning
•Sprint review
Stop doing •Sprint retrospective
•Daily scrum meeting
This is just one Artifacts
of many ways to Continue doing
do a sprint •Product backlog
retrospective. •Sprint backlog
•Burndown charts
Mountain Goat Software, LLC Mountain Goat Software, LLC

29 30

5
 8/9/22

Product backlog A sample product backlog

Backlog item Estimate
•The requirements Allow a guest to make a reservation 3
•A list of all desired work on
the project As a guest, I want to cancel a reservation. 5
•Ideally expressed such that As a guest, I want to change the dates of a
each item has value to the 3
users or customers of the reservation.
product As a hotel employee, I can run RevPAR
8
•Prioritized by the product reports (revenue-per-available-room)
owner Improve exception handling 8
This is the
•Reprioritized at the start of ... 30
each sprint
product backlog ... 50
Mountain Goat Software, LLC Mountain Goat Software, LLC

31 32

The sprint goal Managing the sprint backlog

• A short statement of what the work will be • Individuals sign up for work of their own choosing
focused on during the sprint • Work is never assigned
Life Sciences • Estimated work remaining is updated daily
Support features necessary for
Database Application population genetics studies.

Make the application run on SQL

Server in addition to Oracle.
Financial services
Support more technical indicators
than company ABC with real-time,
streaming data.

Mountain Goat Software, LLC Mountain Goat Software, LLC

33 34

Managing the sprint backlog A sprint backlog

• Any team member can add, delete or change the
sprint backlog Tasks Mon Tues Wed Thur Fri
• Work for the sprint emerges Code the user interface 8 4 8
• If work is unclear, define a sprint backlog item with Code the middle tier 16 12 10 4
a larger amount of time and break it down later Test the middle tier 8 16 16 11 8
• Update work remaining as more becomes known Write online help 12
Write the foo class 8 8 8 8 8
Add error logging 8 4

Mountain Goat Software, LLC Mountain Goat Software, LLC

35 36

6
 8/9/22

Tasks Mon Tues Wed Thur Fri

A sprint burndown chart Code the user interface 8 4 8
Code the middle tier 16 12 10 7
Test the middle tier 8 16 16 11 8
Write online help 12
Hours

50
40

30

Hours
20
10
0
Mon Tue Wed Thu Fri

Mountain Goat Software, LLC Mountain Goat Software, LLC

37 38

Scalability
• Typical individual team is 7 2 people
• Scalability comes from teams of teams
• Factors in scaling
• Type of application
• Team size
• Team dispersion
• Project duration
• Scrum has been used on multiple 500+ person
projects
Mountain Goat Software, LLC

39