Ralph jocham agile portfolio based release trains

  • Published on
    13-Jan-2015

  • View
    376

  • Download
    3

Embed Size (px)

DESCRIPTION

 

Transcript

  • 1. Twitter Hashtag #ATBuc12Ralph Jocham effective agile. ralph.jocham@effectiveagile.com

2. Agile Portfolio basedRelease TrainsRalph Jocham effective agile. ralph.jocham@effectiveagile.com 3. 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@rjocham effective agile. ralph.jocham@effectiveagile.com 4. 1 ProductEasy1 Project 1 Scrum Team25-Oct-12 effective agile.4 5. 1 Product OK1 Projectn Scrum Teams25-Oct-12 effective agile.5 6. n Productsn Projects?n Scrum Teams25-Oct-12 effective agile. 6 7. Work is organizedby activity Plan Analyze Design Code Test Release Big BatchesMajor Releases25-Oct-12 effective agile. 7 8. Phases and FTE/Multitasking Number of emergency projects that must start reducesleads toNumber of new projectsthat start reduces Number of active projects leads to perpetuatesreducesleads to Number of completed projectsEase of managing the portfolio leads toleads to Ability of people to finish projects quicklyCompetition for peoples timereduces(source: Johanna Rothman) 25-Oct-12 effective agile. 8 9. 100% 50% 40% Planning Analysis Design Design Dev Tes@ng Dev Release Release Tes@ng Release Major Release Planning Analysis Design Dev Dev Tes@ng Release Major Release 100% Planning Analysis Design Dev Tes@ng Release Major Release Planning Analysis Design Dev Tes@ng Release Major Release (Source: Gerald Weinberg, Quality SoLware Management: Systems Thinking) V1 2012 Ralph Jocham 25-Oct-12 effective agile. effective agile.www.effectiveagile.com 10. n Productsn Projects?n Scrum Teams25-Oct-12 effective agile. 10 11. Scrum is Fractal25-Oct-12 effective agile. 11 12. We can apply the sameprinciples of the micro atmacro level Strategy PortfolioProduct PrioritizePortfolio Backlog Release PrioritizeSprintDaily Product Backlog25-Oct-12 effective agile.12 13. Is this enough?25-Oct-12 effective agile. 13 14. Three primary release strategiesLots of changes, happen infrequently, Majorfreezes other work, relatively stalefunctionality, high customer absorptioncosts.Minor Lots of broad changes, happen moreMinor Minor frequently, often not cohesive, oftenMinor bug fixes instead of new functionality.Individual pieces of functionality,happen often, most important piece ofFunctionalfunctionality at the time, relatively lowcustomer absorption costs.(source: ADM)25-Oct-12 effective agile. 14 15. Prioritized Portfoliowith Functional Releases25-Oct-12 effective agile. 15 16. Two problems to solveHow can we do this?What does this mean for our requirements?25-Oct-12 effective agile.16 17. Classic approachExternal ReleaseRelease DocsDrop 1 to Drop 2 to System test and bugMRD PRDSRS Devfix QAQATest Drop Test Drop1 2 Ports, Certs(source: Dean Leffingwell)25-Oct-12 effective agile. 17 18. Wanted approachStart External ReleaseRelease DocsSprint Sprint Sprint HardenSprintSprintSprint Harden Ports, Certs(source: Dean Leffingwell) TargetExternal Release External Release Release Docs Release DocsSprint SprintSprintSprint SprintSprintSprintSprintPorts, Certs Ports, Certs25-Oct-12 effective agile.18 19. How can we do this1. More Frequent releases at least four per calendar yearExternal Release2. Develop a cadence for the releases3. Automate the build and deploy process Release DocsSprint SprintSprintSprint4. Enforce a prudent Definition of Done5. Reduce the cycle time continuously Ports, Certs Release Train Release 4 Release 3 Release 2 Release 1 25-Oct-12 effective agile.19 20. What does this meanfor our requirements1. We need features for every release train 2. Break down the projects into the contained features 3. Reduce the feature granularity 4. Assign right sized work to Dev Teams (not resources to problems) No more Projects25-Oct-12 effective agile. 20 21. $$ F5F6 Project 1Project 2Project 3$$ F3 $$$F1 $F3$F3$$ F5 $F4F1 F4 F1 F4 $ $$$ $ F4$ F3 $ F5 F2 $ F5 $ F5F2 $ F2 F3$F1 $ F5$F6F2$ $ F1F3$ $$ F1F4priorising by businessF4value and capacity Project= projectF4= feature of project $ = predicted ROI of feature Software Development Black Boxcapacity is 4 features per releaseF2F3F1F3ReleaseF1F5F4F4TrainRelease 4Release 3Release 2 Release 11 per month 25-Oct-12 effective agile.21 22. Steering Portfolio Backlog StrategicBoard / PMOPortfolioHigh-Level Requirements(Epics) PortfolioManagement Tactic/Strategic Area POTeam C Program BacklogProgramProduct Team B Understood ManagementRequirements Team A(Features)Release Management Release n+1 Release nTactical Team CScrumTeams Team BacklogsProduct Team B Owner, Scrum TeamMaster, DevTeam Release Team A Scrum Teamsare cross-functional Executable Teams (Dev, Test,RequirementsBA, QA, )(User Stories)Sprint nSprint n+1Con@nuous Integra@on / Deployment effective agile. 23. Tactic/StrategicArea POTeam C Program BacklogProgram Product Understood Team B ManagementRequirementsTeam A(Features)Release Management Release n+1Release n TacticalTeam C ScrumTeams Team BacklogsProductTeam B Owner, Scrum TeamMaster, DevTeamReleaseTeam A Scrum Teamsare cross-functional Executable Teams (Dev, Test,RequirementsBA, QA, )(User Stories) Sprint nSprint n+1 IntegrationScrum effective agile. 24. TacticalTeam CScrum TeamsTeam BacklogsProductTeam B Owner, ScrumTeamMaster, DevTeamReleaseTeam AScrum Teams are cross-functionalExecutableTeams (Dev, Test, Requirements BA, QA, ) (User Stories) Sprint nSprint n+1Release Train IntegrationScrum LifeCycle effective agile. 25. 100% 50% 40% Planning Analysis Design Design Dev Tes@ng Dev Release Release Tes@ng Release Major Release Planning Analysis Design Dev Dev Tes@ng Release Major Release 100% Planning Analysis Design Dev Tes@ng Release Major Release Planning Analysis Design Dev Tes@ng Release Major Release Point Release Point Release V1 V1.5 Point Point Release Release V4 V4.2 FR FR FR FR FR FR FR FR FR FR FR FR FR V1 2012 Ralph Jocham effective agile.www.effectiveagile.com 26. Questions?Ralph Jocham www.eec*veagile.com effective agile. ralph.jocham@eec@veagile.com @rjocham 25-Oct-12 effective agile.26 27. References Manage your Project Por_olio: Increase Your Capacity and Finish More Projects, Johanna Rothman, Pragma@c Programmers, 2009 Scaling SoLware Agilty: Best Prac@ces for Large Enterprises, Dean Lengwell, Addison-Wesley, 2007 SoLware in 30 Days: How Agile Managers Beat the Odds, Delight Their Customers and Leave the Compe@tors in the Dust, Ken Schwaber & Je Sutherland, Wiley, 2012 25-Nov-2011 effective agile. 27