empiricism with scrum
TRANSCRIPT
Ralph Jocham • Started as programmer; discovered process as a problem early on • First Unified Process with UML • Agile since 2000 with XP • Scrum in 2003 • Oracle, LinkedIn, Roche, Google, The Gap, Swisscom, Texas Instruments, Siemens Medical,
ThoughtWorks, JPMorganChase • Did come around, different cultures and domains • Founder of effective agile. • Trainer with Scrum.org
13-‐Nov-‐12 effective agile. 3
Plan
Analyze
Design
Code
Test
Release
13-‐Nov-‐12 effective agile. 4
Work is organized by activity
è Big Batches
Plan Analyze Design Code Test Release
13-‐Nov-‐12 effective agile. 5
Is this the right approach for software
development?
Big Batches
13-‐Nov-‐12 effective agile. 6
Scientific Management Is this the right
approach for software development? Command and
Control
13-‐Nov-‐12 effective agile. 7
Scientific Management
13-‐Nov-‐12 effective agile. 8
Simple Complicated
Complex
Chaos
Requ
iremen
ts
Technology close to certainty
far from certainty
close to
agreem
ent
far from
agreem
ent
Simple
Complicated
Chaos
Complex
Sense Categorize Respond
Sense Analyze Respond
Probe Sense
Respond
Best PracDces
Good PracDces Emergent
Act Sense
Respond
Novel
(source: Dave Snowden, IBM)
Cynefin
Complexity Stacey Graph
(source: Ralph Stacey, University of Herfordshire)
Defined Empirical
13-‐Nov-‐12 effective agile. 9
Demming Cycle
35% of Requirements Change
25-‐Nov-‐2011 effective agile. 10
>60% of features are rarely or never used
(source: Standish Group)
25-‐Nov-‐2011 effective agile. 11
Value
13-‐Nov-‐12 effective agile. 12
Original Vision
Original SoluDon
Sprint 11 Sprint 2
Sprint n Sprint n+1
AddiDo
nal V
alue
Welcoming change/ Coping with Complexity
13-‐Nov-‐12 effective agile. 13
13-‐Nov-‐12 effective agile. 14
August 1970
13-‐Nov-‐12 effective agile. 15
13-‐Nov-‐12 effective agile. 16
Plan Analyze Design Code Test Release
Defined
Waterfall (Defined)"Plan for the entire project up-front
V-‐Model
Hermes MIL-‐STD-‐2167A
GAM-‐T-‐17 JSP-‐188
13-‐Nov-‐12 effective agile. 17
Plan Analyze Design Code Test Release
Defined
Waterfall (Defined)"Plan for the entire project up-front
V-‐Model
Hermes MIL-‐STD-‐2167A
GAM-‐T-‐17 JSP-‐188
13-‐Nov-‐12 effective agile. 18
Plan Analyze Design Code Test Release
Defined
Waterfall (Defined)"Plan for the entire project up-front
V-‐Model
Hermes
GAM-‐T-‐17 JSP-‐188
MIL-‐STD-‐498
Defined vs Emperical
13-‐Nov-‐12 effective agile. 19
Scrum (Empirical)"
Waterfall (Defined)"Plan for the entire project up-front
Plan a little for the entire project and then a little for each Sprint"
(source: ADM)
intern
extern
intern
extern
intern
extern
Plan Analyze Design Code Test Release
Plan
Plan
Plan Design Code Test
Release
Plan
Plan Design Code Test
Release
Plan
Plan Design Code Test
Release
Plan
Plan Design Code Test
Release
Higher Chance of Success
13-‐Nov-‐12 effective agile. 20
(source: ADM)
0.9
0.5
0.1
Defined Empirical
Edge of Chaos
Complexity
Low Medium High
Probality of Success
Why a higher Change?
13-‐Nov-‐12 effective agile. 21
(source: ADM)
Visibility Ability to Change
Business Value Risk
Waterfall Scrum
• Scrum (n): A framework within which people can address complex problems, and producDvely and creaDvely develop products of the highest possible value.
(source: ADM)
A simple Definition of Scrum
13-‐Nov-‐12 effective agile. 22
Framework
13-‐Nov-‐12 effective agile. 23
Roles
• Product Owner • Dev 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
13-‐Nov-‐12 effective agile. 24
Roles Product Owner Development Team Scrum Master
ArDfacts Product Backlog Sprint Backlog Increment
Events Sprint Planning Sprint Daily Scrum Sprint Review RetrospecDve
Product Backlog
Sprint Planning MeeDng
Sprint Backlog Sprint
Increment
Review
RetrospecDve
Daily Scrum
ScrumMaster
(source: ADM)
PotenDally Releasable
DefiniDon of Done
Dev
Release Planning Design Release Analysis Dev TesDng
Planning Design Release Analysis TesDng
Design Dev TesDng Release
100%
50% 40%
Planning Design Release Analysis Dev TesDng
Planning Design Release Analysis Dev TesDng
100%
Major Release
Major Release
Major Release
Point Release V1
Point Release V4
Point Release V1.5
Point Release V4.2
Major Release
FR
FuncDonal Release FR FR
FR
FR
FR
FR
FR
Dev
FR V1 © 2012 Ralph Jocham effective agile. www.effectiveagile.com
Stop
Cost of fixing a Bug
ConstrucDon
Detailed Design
Architecture
Requirements
Requirements Architecture
Detailed Design ConstrucDon
Maintenance
ConstrucDon
Detailed Design
Architecture
Requirements
25-‐Nov-‐2011 effective agile. 26
(source: Barry Boehm)
13-‐Nov-‐12 effective agile. 27
Reporting
Reporting
13-‐Nov-‐12 effective agile. 28
Questions?
13-‐Nov-‐12 effective agile. 29
hgp://www.scrum.org/Scrum-‐Guides
Ralph Jocham www.effecHveagile.com
effective agile. [email protected] @rjocham
25-‐Nov-‐2011 effective agile. 30