agile portfolio based release trains by ralph jocham
DESCRIPTION
"Agile Portfolio Based Release Trains" by Ralph Jocham, SCRUM.org Certified SCRUM Trainer and founder of Effective Agile #AgileGreece Meetup http://www.meetup.com/Agile-Greece/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
10-‐Apr-‐14 effective agile. 3
Plan
Analyze
Design
Code
Test
Release
10-‐Apr-‐14 effective agile. 4
Work is organized by activity
è Big Batches
Plan Analyze Design Code Test Release
>60% of features are rarely or never used
(source: Standish Group)
25-‐Nov-‐2011 effective agile. 5
Defined vs Emperical
10-‐Apr-‐14 effective agile. 6
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: effecGve agile)
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
Value
10-‐Apr-‐14 effective agile. 7
Original Vision
Original SoluGon
Sprint 11 Sprint 2
Sprint n Sprint n+1
AddiGo
nal V
alue
Welcoming change/ Coping with Complexity
Dev
Release Planning Design Release Analysis Dev TesGng
Planning Design Release Analysis TesGng
Design Dev TesGng Release
100%
50% 40%
Planning Design Release Analysis Dev TesGng
Planning Design Release Analysis Dev TesGng
100%
Major Release
Major Release
Major Release
Major Release
Dev
10-‐Apr-‐14 effective agile.
(Source: Gerald Weinberg, Quality SoVware Management: Systems Thinking) V1 © 2012 Ralph Jocham effective agile. www.effectiveagile.com
10-‐Apr-‐14 effective agile. 9
(source: Johanna Rothman)
Number of active projects
Ability of people to finish projects quickly Competition for people’s time
Ease of managing the portfolio Number of completed projects
Number of new projects that start
leads to
leads to
leads to
reduces leads to
reduces
leads to
reduces
Number of emergency projects that must start
reduces
perpetuates
Complex Adaptive System
10-‐Apr-‐14 effective agile. 10
F3 $
F2 $
F1 $
F3 $
Project 1 Project 2 Project 3
F4 $
F2 $
F3 $
F1 $
F5 $
F1 $
F3 $
F5 $ F4
$
F4 $
F2 $
F1 $
F5 $
F3
$
F6
$
Software Development Black Box
Release 1 Release 2 Release 3 Release 4
F4 $
F4 $
F1 $
F5 $ F2
$
F1 $
F4 $
F6
$F5
$
F3
$
F5 $
$ = predicted ROI of feature
Project = project
F4 = feature of project
capacity is 4 features per release F3 F1
F4 F4 F1
F3
F5
F2
priorising by business value and capacity
Release Train
1 per month
Dev
Release Planning Design Release Analysis Dev TesGng
Planning Design Release Analysis TesGng
Design Dev TesGng Release
100%
50% 40%
Planning Design Release Analysis Dev TesGng
Planning Design Release Analysis Dev TesGng
100%
Major Release
Major Release
Major Release
Point Release V1
Point Release V4
Point Release V1.5
Point Release V4.2
Major Release
Dev
V1 © 2012 Ralph Jocham effective agile. www.effectiveagile.com
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
Questions?
10-‐Apr-‐14 effective agile. 12
Ralph Jocham effective agile.
www.effec*veagile.com [email protected]
@rjocham
25-‐Nov-‐2011 effective agile. 13
References
• Manage your Project Por]olio: Increase Your Capacity and Finish More Projects, Johanna Rothman, PragmaGc Programmers, 2009
• Scaling SoVware Agilty: Best PracGces for Large Enterprises, Dean Leffingwell, Addison-‐Wesley, 2007
• SoVware in 30 Days: How Agile Managers Beat the Odds, Delight Their Customers and Leave the CompeGtors in the Dust, Ken Schwaber & Jeff Sutherland, Wiley, 2012