Scrum is an agile framework that can help address complex problems and develop high-value products. It consists of roles, artifacts, and events used to structure development into sprints. The roles include the product owner, development team, and scrum master. Artifacts include the product backlog, sprint backlog, and increment. Events include sprint planning, daily scrums, sprint reviews, and retrospectives. Scrum takes an empirical, transparent, inspect-and-adapt approach to product development through short iterations.

1. A short introduction to
Scrum
Ralph Jocham effective agile. ralph@effectiveagile.com

2. A simple Definition of Scrum
• Scrum (n): A framework within which
people can address complex problems,
and productively and creatively develop
products of the highest possible value.
(source: ADM)
9-Jun-11 effective agile. 2

3. Framework
Roles Artifacts Events
• Product • Increment
• Sprint
Owner
• Product • Sprint
• Team
Backlog
Planning
• Scrum Master
• Sprint • Daily Scrum
Backlog
• Sprint Review
• Retrospective
(source: ADM)
9-Jun-11 effective agile. 3

4. Roles, Artifacts and Events
in Action Review
Roles
Product Owner
Team
Scrum Master Retrospective
Increment
Daily
Artifacts Scrum
Product Backlog
Sprint Backlog
Sprint
Increment Backlog
Sprint
Sprint
Planning
Meeting
Events Product
Sprint Planning Backlog
Sprint
Daily Scrum
Sprint Review
Retrospective ScrumMaster
(source: ADM)
9-Jun-11 effective agile. 4

5. Complex
far from
agreement
Complex Complicated
Chaos Probe Sense
Sense Analyze
Respond
Requirements
Respond
Complex Emergent Good Practices
Chaos Simple
Act Sense
Sense Categorize
agreement
Respond Respond
Simple Complicated
close to
Novel Best Practices
close to
certainty
Technology far from
certainty
(source: IBM)
9-Jun-11 effective agile. 5

6. Defined vs Emperical
Waterfall (Defined)"
Plan for the entire
Plan Analyze Design Code Test Release
project up-front
Scrum (Empirical)" Analyze Analyze Analyze Analyze
Design Design Design Design
Plan a little for the
Plan
Plan
Plan
Plan
Plan
Code Code Code Code
entire project and then Test Test Test Test
a little for each Sprint" Release Release Release Release
intern intern intern
extern extern extern
(source: ADM)
9-Jun-11 effective agile. 6

7. Empirical: Higher Chance of
Success
0.9
Probality of
Success
0.5 Empirical
Defined
Edge of
Chaos
0.1
Low Medium High
Complexity
(source: ADM)
9-Jun-11 effective agile. 7

8. The four legs of Scrum
• Emperical
• Transparency
• Inspection
• Adaption
9-Jun-11 effective agile. 8

9. Value
Original Solution Domain
Welcoming Change/
Coping with Complexity
Spri nt n +1
nt n Spri
Additional Value
2
Spri Sprint
n t1
Original Vision
9-Jun-11 effective agile. 9

10. Why Scrum
• Releases take longer and longer • Agility – flexibility to turn on a dime
• Realease schedules slip • Improved productivity and quality
• Stabilization at end of release takes • Early elimination of risk
longer and longer • Early realization of value
• Planning seems to take to long • Always knowing exactly where you are in a
• Changes are hard to introduce mid development/deployment cycle
release • Easier to make changes
• Quality is detoriating • Reduced waste
• Dissatisfied, alienated customers • Lean products that reach market faster and
• Death marches are hurting morale are more targeted
• Products becoming prohibitevly • Increased Return on Investment (ROI)
expensive to support and enhance • Engaged, empowered workers
• Reduced Total Cost of Ownership (TCO)
9-Jun-11 effective agile. 10

11. A simple Definition of Scrum
• Scrum (n): A framework within which
people can address complex problems,
and productively and creatively develop
products of the highest possible value.
(source: ADM)
9-Jun-11 effective agile. 11

12. Questions?
9-Jun-11 effective agile. 12