Embed Size (px)
DESCRIPTION
Citation preview
• Scrum (n): A framework within which people can address complex problems, and productively and creatively develop products of the highest possible value.
(source: ADM)
A simple Definition of Scrum
9-Jun-11 effective agile. 2
Framework
9-Jun-11 effective agile. 3
Roles • Product
Owner • Team • Scrum Master
Artifacts • Increment • Product
Backlog • Sprint
Backlog
Events • Sprint • Sprint
Planning • Daily Scrum • Sprint Review • Retrospective
(source: ADM)
Roles, Artifacts and Events in Action
9-Jun-11 effective agile. 4
Roles Product Owner Team Scrum Master
Artifacts Product Backlog Sprint Backlog Increment
Events Sprint Planning Sprint Daily Scrum Sprint Review Retrospective
Product Backlog
Sprint Planning Meeting
Sprint Backlog Sprint
Increment
Review
Retrospective
Daily Scrum
ScrumMaster
(source: ADM)
Complex
9-Jun-11 effective agile. 5
Simple Complicated
Complex
Chaos
Req
uire
men
ts
Technology close to certainty
far from certainty
clos
e to
ag
reem
ent
far f
rom
ag
reem
ent
Simple
Complicated
Chaos
Complex
Sense Categorize Respond
Sense Analyze Respond
Probe Sense
Respond
Best Practices
Good Practices Emergent
Act Sense
Respond Novel
(source: IBM)
Defined vs Emperical
9-Jun-11 effective agile. 6
Scrum (Empirical)"
Waterfall (Defined)"
Plan Analyze Design Code Test Release Plan for the entire project up-front
Plan a little for the entire project and then a little for each Sprint"
Plan
Analyze Design Code Test
Release
Plan
Plan
Analyze Design Code Test
Release
Plan
Analyze Design Code Test
Release
Plan
Analyze Design Code Test
Release
(source: ADM)
intern
extern
intern
extern
intern
extern
Empirical: Higher Chance of Success
9-Jun-11 effective agile. 7
(source: ADM)
0.9
0.5
0.1
Defined Empirical
Edge of Chaos
Complexity Low Medium High
Probality of Success
The four legs of Scrum
• Emperical
• Transparency • Inspection • Adaption
9-Jun-11 effective agile. 8
Value
9-Jun-11 effective agile. 9
Original Vision
Original Solution Domain
Sprint 1 Sprint 2
Sprint n Sprint n+1
Add
ition
al V
alue
Welcoming Change/ Coping with Complexity
Why Scrum
9-Jun-11 effective agile. 10
• Releases take longer and longer • Realease schedules slip • Stabilization at end of release takes
longer and longer • Planning seems to take to long • Changes are hard to introduce mid
release • Quality is detoriating • Dissatisfied, alienated customers • Death marches are hurting morale • Products becoming prohibitevly
expensive to support and enhance
• Agility – flexibility to turn on a dime • Improved productivity and quality • Early elimination of risk • Early realization of value • Always knowing exactly where you are in a
development/deployment cycle • Easier to make changes • Reduced waste • Lean products that reach market faster and
are more targeted • Increased Return on Investment (ROI) • Engaged, empowered workers • Reduced Total Cost of Ownership (TCO)
• Scrum (n): A framework within which people can address complex problems, and productively and creatively develop products of the highest possible value.
(source: ADM)
A simple Definition of Scrum
9-Jun-11 effective agile. 11
Questions?
9-Jun-11 effective agile. 12
