More Related Content
Similar to Getting Agile with Scrum
Similar to Getting Agile with Scrum (20)
Getting Agile with Scrum
- 2. ® © 2003–2012 Mountain Goat Software®
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
tries to go the distance as a unit, passing the
competitive requirements.”
2
- 3. ® © 2003–2012 Mountain Goat Software®
Source: “How Apple Does It,” Time Magazine,
October 24, 2005 by Lev Grossman
“Apple employees talk incessantly about what
they call ‘deep collaboration’ or ‘cross-
pollination’ or ‘concurrent engineering.’
“Essentially it means that products don’t pass
from team to team. There aren’t discrete,
sequential development stages. Instead, it’s
simultaneous and organic.
“Products get worked on in parallel by all
departments at once—design, hardware,
software—in endless rounds of interdisciplinary
design reviews.”
3
- 4. ® © 2003–2009 Mountain Goat Software®
Yahoo
Google
Electronic Arts
IBM
Lockheed Martin
Philips
Siemens
Nokia
Capital One
BBC
Intuit
Apple
Nielsen Media
First American Corelogic
Qualcomm
Texas Instruments
John Deere
Lexis Nexis
Time Warner
Turner Broadcasting
Oce
4
- 5. ® © 2003–2009 Mountain Goat Software®
In-house development
Contract development
Fixed-price projects
Financial applications
applications
24x7 systems with 99.999%
uptime requirements
the Joint Strike Fighter
Video game development
systems
Network switching
applications
ISV applications
applications in use
5
- 6. ® © 2003–2009 Mountain Goat Software®
Characteristics
“sprints”
Uses generative rules to create an agile
6
- 7. ® © 2003–2012 Mountain Goat Software®
Project noise level
Simple
Complex
Anarchy
Com
plicated
Technology
Requirements
Agreement
Close to
Agreement
Closeto
Certainty
Certainty
Strategic Management and
Organizational Dynamics
Agile Software Development with Scrum
® © 2003–2009 Mountain Goat Software®
7
- 8. ® © 2003–2012 Mountain Goat Software®
Scrum
Cancel
Return
Sprint
1-4 weeks
Return
Sprint goal
Sprint
product increment
Product
Vouchers
Vouchers
Cancel
24 hours
8
- 9. ® © 2003–2009 Mountain Goat Software®
Sprints
“sprints”
Typical duration is 2–4 weeks or a calendar
month at most
Product is designed, coded, and tested during
the sprint
9
- 10. ® © 2003–2009 Mountain Goat Software®
Sequential vs. overlapping
development
and Nonaka. Harvard Business Review, January 1986.
one thing at a time...
...Scrum teams do a little
Requirements Design Code Test
10
- 11. ® © 2003–2009 Mountain Goat Software®
No changes during a sprint
Plan sprint durations around how long you can
Change
11
- 12. ® © 2003–2012 Mountain Goat Software®
Product owner
ScrumMaster
Team
Roles
Sprint planning
Sprint review
Sprint retrospective
Daily scrum meeting
Ceremonies
Burndown charts
12
- 13. ® © 2003–2012 Mountain Goat Software®
Sprint planning
Sprint review
Sprint retrospective
Daily scrum meeting
Ceremonies
Burndown charts
Product owner
ScrumMaster
Team
Roles
13
- 14. ® © 2003–2009 Mountain Goat Software®
Product owner
Makes scope vs. schedule decisions
project
Adjust
needed
Accept or reject work results
14
- 15. ® © 2003–2009 Mountain Goat Software®
The ScrumMaster
and practices
Removes impediments
15
- 16. ® © 2003–2009 Mountain Goat Software®
The team
Typically 5-9 people
Programmers, testers, user experience designers, etc.
M
16
- 17. ® © 2003–2012 Mountain Goat Software®
Product owner
ScrumMaster
Team
Roles
Burndown charts
Sprint planning
Sprint review
Sprint retrospective
Daily scrum meeting
Ceremonies
17
- 18. ® © 2003–2012 Mountain Goat Software®
Sprint planning meeting
Sprint
backlog
Sprint
goal
Who
• Team, ScrumMaster, & Product
Owner
Agenda
• Discuss top priority product
backlog items
• Team selects which to do
Why
• Know what will be worked on
• Understand it enough to do it
18
- 19. ® © 2003–2009 Mountain Goat Software®
Sprint planning
commit to completing
High-level design is considered
As a vacation
planner, I want to
see photos of the
hotels.
19
- 20. ® © 2003–2009 Mountain Goat Software®
The daily scrum
Parameters
Daily
15-minutes
Stand-up
Whole world is invited
owner, can talk
Helps avoid other unnecessary meetings
20
- 21. ® © 2003–2009 Mountain Goat Software®
Everyone answers 3 questions
These are not
What did you do yesterday?
1
What will you do today?
2
Is anything in your way?
3
21
- 22. ® © 2003–2009 Mountain Goat Software®
The sprint review
Team presents what it accomplished during
the sprint
2-hour prep time rule
No slides
Whole team participates
Invite the world
22
- 23. ® © 2003–2009 Mountain Goat Software®
Sprint retrospective
Periodically take a look at what is and is not
working
Typically around 30 minutes
Whole team participates
ScrumMaster
Product owner
Team
23
- 24. ® © 2003–2009 Mountain Goat Software®
Start / Stop / Continue
Whole team gathers and discusses what they’d
Start doing
Stop doing
Continue doing
This is just one
of many ways
to do a sprint
retrospective.
24
- 25. ® © 2003–2012 Mountain Goat Software®
Product owner
ScrumMaster
Team
Roles
Sprint planning
Sprint review
Sprint retrospective
Daily scrum meeting
Ceremonies
Burndown charts
25
- 26. ® © 2003–2009 Mountain Goat Software®
The requirements
the project
Ideally expressed such that
each item has value to the
product
owner
each sprintThis is the
26
- 27. ® © 2003–2012 Mountain Goat Software®
Backlog item Estimate
Allow a guest to make a reservation 3
As a guest, I want to cancel a reservation. 5
reservation.
3
As a hotel employee, I can run RevPAR
8
Improve exception handling 8
... 30
... 50
27
- 28. ® © 2003–2009 Mountain Goat Software®
Sprint goal
A short statement
of what the work
will be focused on
during the sprint
Sprint 8
The checkout process—pay
for an order, pick shipping,
order gift wrapping, etc.
Sprint 7
Implement basic shopping
cart functionality including
add, remove, and update.
28
- 29. ® © 2003–2009 Mountain Goat Software®
Work is never assigned
Estimated work remaining is updated daily
29
- 30. ® © 2003–2012 Mountain Goat Software®
Tasks
Code the middle tier
Test the middle tier
Write online help
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
30
- 31. ® © 2003–2012 Mountain Goat Software®
0
200
400
600
800
1,000 4/29/02
5/6/02
5/13/02
5/20/02
5/24/02
Hours
31
- 32. ® © 2003–2012 Mountain Goat Software®
Hours
40
30
20
10
0
Mon Tue Wed Thu Fri
Tasks
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
32
- 33. ® © 2003–2009 Mountain Goat Software®
Typical individual team is 7 ± 2 people
Factors in scaling
Team dispersion
Project duration
people
33
- 34. ® © 2003–2012 Mountain Goat Software®
Scaling through the Scrum
34
- 35. ® © 2003–2012 Mountain Goat Software®
Programmers
ScrumMasters
UI Designers
Testers
DBAs
Communities of
Practice help scale
and cut across
Scrum teams
35
- 36. ® © 2003–2009 Mountain Goat Software®
A Scrum reading list
Agile Estimating and Planning
Agile Game Development with Scrum
Agile Product Ownership
Agile Retrospectives
AgileTesting:A Practical Guide forTesters and AgileTeams
Crispin and Janet Gregory
Coaching AgileTeams
Essential Scrum
Succeeding with Agile: Software Development using Scrum
Cohn
User Stories Applied for Agile Software Development
36
- 38. ® © 2003–2012 Mountain Goat Software®
mike@mountaingoatsoftware.com
www.mountaingoatsoftware.com
twitter: mikewcohn
Mike Cohn
38