An Introduction To Scrum: Presented by
An Introduction To Scrum: Presented by
Presented by
<you>
<date>
• Financial applications
• Websites
• ISO 9001-certified
• Handheld software
applications • Mobile phones
• Embedded systems • Network switching applications
• 24x7 systems with 99.999% • ISV applications
uptime requirements
• Some of the largest applications in
• the Joint Strike Fighter use
Individuals
Individuals and
and over Process
Process and
and tools
tools
interactions
interactions
Comprehensive
Comprehensive
Working
Working software
software over
documentation
documentation
Customer
Customer collaboration
collaboration over Contract
Contract negotiation
negotiation
Responding
Responding to
to change
change over Following
Following aa plan
plan
Source: www.agilemanifesto.org
Mountain Goat Software, LLC
Project noise level
Far from
Agreement
Anarchy
Requirements
Complex
Co
m
pl
ica Source: Strategic Management and
ted Organizational Dynamics by Ralph Stacey
in Agile Software Development with Scrum
Agreement
Technology
Close to
Certainty
Far from
Certainty
Mountain Goat Software, LLC
Scrum 24 hours
Sprint
2-4 weeks
Sprint goal
Return
Sprint Potentially shippable
Cancel
Return backlog product increment
Gift
Coupons
wrap
Gift
Cancel
wrap Coupons
Product
backlog
Image available at
www.mountaingoatsoftware.com/scrum
Mountain Goat Software, LLC
Sprints
Change
As
As aa vacation
vacation Code the middle tier (8 hours)
planner,
planner, II want
want to
to Code the user interface (4)
see
see photos
photos of
of the
the
Write test fixtures (4)
Code the foo class (6)
hotels.
hotels. Update performance tests (4)
2
What will you do
do today?
today?
3
Is anything in your way?
• These are not status for the ScrumMaster
• They are commitments in front of peers
Mountain Goat Software, LLC
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
Mountain Goat Software, LLC
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
Stop doing
This is just one
of many ways to Continue doing
do a sprint
retrospective.
Tasks
Tasks Mon
Mon Tues
Tues Wed
Wed Thur
Thur Fri
Fri
Code the user interface 8 4 8
Code the middle tier 16 12 10 4
Test the middle tier 8 16 16 11 8
Write online help 12
Write the foo class 8 8 8 8 8
Add error logging 8 4
50
40
30
Hours
20
10
0
Mon Tue Wed Thu Fri
• www.mountaingoatsoftware.com/scrum
• www.scrumalliance.org
• www.controlchaos.com
• [email protected]
t
You can remove this (or any slide) bu
re
you must credit the source somewhe
d
in your presentation. Use the logo an
r
company name (as at bottom left, fo
re
example) or include a slide somewhe
saying that portions (or all) of your
presentation are from this source.
Thanks.