Agile Portfolio Based Release Trains by Ralph Jocham
2 likes1,069 views
Ralph Jocham, founder of Effective Agile, emphasizes the importance of agile methodologies, particularly Scrum, and the shift from defined processes to empirical approaches in software development. The document discusses challenges in project management, such as the inefficiency of large batches and the proportion of features that go unused. Jocham provides insights on project portfolio management, capacity, and prioritization based on business value to enhance project completion rates.
![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](https://image.slidesharecdn.com/featuresoverprojects-140410060749-phpapp02/85/Agile-Portfolio-Based-Release-Trains-by-Ralph-Jocham-13-320.jpg)
Agile Portfolio Based Release Trains by Ralph Jocham
- 1. Value Features over Projects effective agile.Ralph Jocham ralph.jocham@effectiveagile.com
- 2. 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
- 3. 10-‐Apr-‐14 effective agile. 3 Plan Analyze Design Code Test Release
- 4. 10-‐Apr-‐14 effective agile. 4 Work is organized by activity è Big Batches Plan Analyze Design Code Test Release
- 5. >60% of features are rarely or never used (source: Standish Group) 25-‐Nov-‐2011 effective agile. 5
- 6. 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
- 7. Value 10-‐Apr-‐14 effective agile. 7 Original Vision Original SoluGon Sprint 11 Sprint 2 Sprint n Sprint n+1 AddiGonal Value Welcoming change/ Coping with Complexity
- 8. 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
- 9. 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 portfolioNumber 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. 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 1Release 2Release 3Release 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 F3F1 F4F4F1 F3 F5 F2 priorising by business value and capacity Release Train 1 per month
- 11. 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
- 12. Questions? 10-‐Apr-‐14 effective agile. 12 Ralph Jocham effective agile. www.effec*veagile.com ralph.jocham@effecGveagile.com @rjocham
- 13. 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