Scrum introduction

Mountain Goat Software, LLC
An Introduction
to Scrum
PRETI, João Paulo D.
08/06/2017

PRETI, João Paulo D.
08/06/2017
Presented by
An Introduction to Scrum

We re losing the relay race
Hirotaka Takeuchi and Ikujiro Nonaka, The New
New Product Development Game , Harvard
Business Review, January 1986.
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.

• 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.
Scrum in 100 words

Scrum origins
• Jeff Sutherland
• Initial scrums at Easel Corp in 1993
• IDX and 500+ people doing Scrum
• Ken Schwaber
• ADM
• Scrum presented at OOPSLA 95 with
Sutherland
• Author of three books on Scrum
• Mike Beedle
• Scrum patterns in PLOPD4
• Ken Schwaber and Mike Cohn
• Co-founded Scrum Alliance in 2002, initially
within the Agile Alliance

Scrum has been used by:
•Microsoft
•Yahoo
•Google
•Electronic Arts
•High Moon Studios
•Lockheed Martin
•Philips
•Siemens
•Nokia
•Capital One
•BBC
•Intuit
•Intuit
•Nielsen Media
•First American Real Estate
•BMC Software
•Ipswitch
•John Deere
•Lexis Nexis
•Sabre
•Salesforce.com
•Time Warner
•Turner Broadcasting
•Oce

Scrum has been used for:
• Commercial software
• In-house development
• Contract development
• Fixed-price projects
• Financial applications
• ISO 9001-certified
applications
• Embedded systems
• 24x7 systems with 99.999%
uptime requirements
• the Joint Strike Fighter
•Video game development
•FDA-approved, life-critical systems
•Satellite-control software
•Websites
•Handheld software
•Mobile phones
•Network switching applications
•ISV applications
•Some of the largest applications in
use

Characteristics
•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
•Uses generative rules to create an agile
environment for delivering projects
•One of the agile processes

The Agile Manifesto–a statement of
values
Process and tools
Individuals and
interactions
over
Following a planResponding to change over
Source: www.agilemanifesto.org
Comprehensive
documentation
Working software over
Contract negotiation
Customer
collaboration
over

Project noise level
Simple
Complex
Anarchy
Technology
Requirements
Far from
Agreement
Close to
Agreement
Closeto
Certainty
Farfrom
Certainty
Source: Strategic Management and
Organizational Dynamics by Ralph Stacey in
Agile Software Development with Scrum by
Ken Schwaber and Mike Beedle.

Scrum
Cancel
Gift wrap
Return
Sprint
2-4 weeks
Return
Sprint goal
Sprint
backlog
Potentially shippable
product increment
Product
backlog
CouponsGift wrap
Coupons
Cancel
24 hours

Putting it all together
Image available at
www.mountaingoatsoftware.com/scrum

Sprints
•Scrum projects make progress in a series of
sprints
• Analogous to Extreme Programming iterations
•Typical duration is 2–4 weeks or a calendar
month at most
•A constant duration leads to a better rhythm
•Product is designed, coded, and tested during
the sprint

Sequential vs. overlapping
development
Source: The New New Product Development Game by Takeuchi
and Nonaka. Harvard Business Review, January 1986.
Rather than doing all of
one thing at a time...
...Scrum teams do a little
of everything all the time
Requirements Design Code Test

No changes during a sprint
•Plan sprint durations around how long you can
commit to keeping change out of the sprint
Change

Scrum framework
•Product owner
•ScrumMaster
•Team
Roles
•Sprint planning
•Sprint review
•Sprint retrospective
•Daily scrum meeting
Ceremonies
•Product backlog
•Sprint backlog
•Burndown charts
Artifacts

Scrum framework
•Sprint planning
•Sprint review
Ceremonies
•Product backlog
•Sprint backlog
•Burndown charts
Artifacts
•Product owner
•ScrumMaster
•Team
Roles

Product owner
•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

The ScrumMaster
•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

The team
•Typically 5-9 people
•Cross-functional:
• Programmers, testers, user experience designers,
etc.
• Members should be full-time
• May be exceptions (e.g., database administrator)

The team
•Teams are self-organizing
• Ideally, no titles but rarely a possibility
•Membership should change only between sprints

•Product owner
•ScrumMaster
•Team
Roles
Scrum framework
•Product backlog
•Sprint backlog
•Burndown charts
Artifacts
•Sprint planning
•Sprint review
Ceremonies

Sprint planning meeting
Sprint prioritization
• Analyze and evaluate product
backlog
• Select sprint goal
Sprint planning
• Decide how to achieve sprint goal
(design)
• Create sprint backlog (tasks) from
product backlog items (user stories
/ features)
• Estimate sprint backlog in hours
Sprint
goal
Sprint
backlog
Business
conditions
Team
capacity
Product
backlog
Technology
Current
product

Sprint planning
• 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 ScrumMaster
• 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)

The daily scrum
•Parameters
• Daily
• 15-minutes
• Stand-up
•Not for problem solving
• Whole world is invited
• Only team members, ScrumMaster, product
owner, can talk
•Helps avoid other unnecessary meetings

Everyone answers 3 questions
•These are not status for the ScrumMaster
• They are commitments in front of peers
What did you do yesterday?
1
What will you do today?
2
Is anything in your way?
3

The sprint review
•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

Sprint retrospective
•Periodically take a look at what is and is not
working
•Typically 15–30 minutes
•Done after every sprint
•Whole team participates
• ScrumMaster
• Product owner
• Team
• Possibly customers and others

Start / Stop / Continue
•Whole team gathers and discusses what
they d like to:
Start doing
Stop doing
Continue doing
This is just one
of many ways to
do a sprint
retrospective.

•Product owner
•ScrumMaster
•Team
Roles
Scrum framework
•Sprint planning
•Sprint review
Ceremonies
•Product backlog
•Sprint backlog
•Burndown charts
Artifacts

Product backlog
•The requirements
•A list of all desired work 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 sprintThis is the
product backlog

User Story Map
Source: https://marketplace.atlassian.com/plugins/com.kretar.jira.plugin.user-story-map/cloud/overview

User Story Map
Source: http://winnipegagilist.blogspot.com.br/2012/03/how-to-create-user-story-map.html

User Story Map
Source: https://pt.slideshare.net/AgileCampSV/agilecamp-silicon-valley-2015-user-story-mapping

User Story Map
Source: http://masteringbusinessanalysis.com/episode-016-user-story-mapping-with-jeff-patton/

User Story Description

As a [user role]
I want to [goal]
so I can [reason]
As a registered user
I want to log in
so I can access subscriber-only content

Source: http://agile.yakubovsky.com/2015/12/user-story-scenarios/

Source: https://jtbd.info/replacing-the-user-story-with-the-job-story-af7cdee10c27

A sample product backlog
Backlog item Estimate
Allow a guest to make a reservation 3
As a guest, I want to cancel a reservation. 5
As a guest, I want to change the dates of a
reservation.
3
As a hotel employee, I can run RevPAR
reports (revenue-per-available-room)
8
Improve exception handling 8
... 30
... 50

Estimate (Story Points vs Task Hours)
• Serve different purposes at different times
• A relation between them may not be advisable
• Story Points
• High level estimation
• Made before sprint planning
• Task Hours
• Low level estimation
• done during sprint planning

Story Points vs Task Hours
https://www.scrumalliance.org/community/articles/2012/august/story-points-versus-task-hours

The sprint goal
•A short statement of what the work will be
focused on during the sprint
Database Application
Financial services
Life Sciences
Support features necessary for
population genetics studies.
Support more technical indicators
than company ABC with real-time,
streaming data.
Make the application run on SQL
Server in addition to Oracle.

Managing the sprint backlog
• Individuals sign up for work of their own choosing
• Work is never assigned
• Estimated work remaining is updated daily

Managing the sprint backlog
• 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

A sprint backlog
Tasks
Code the user interface
Code the middle tier
Test the middle tier
Write online help
Write the foo class
Mon
8
16
8
12
8
Tues
4
12
16
8
Wed Thur
4
11
8
4
Fri
8
8
Add error logging
8
10
16
8
8

A sprint burndown chartHours

Hours
40
30
20
10
0
Mon Tue Wed Thu Fri
Tasks
Code the user interface
Code the middle tier
Test the middle tier
Write online help
Mon
8
16
8
12
Tues Wed Thur Fri
4
12
16
7
11
8
10
16 8
50

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

Scaling through the Scrum of scrums

Scrum of scrums of scrums

Scrum introduction

More Related Content

Scrum introduction