Downloaded 581 times
Uploaded byLiminalArc
Agile Transformation v1.27
The document discusses goals for adopting agile practices like predictability, quality, early ROI, lower costs, and innovation. It then covers considerations for transformation based on organization size, dependencies between teams, and resistance to change. Finally, it outlines key elements of transformation including backlogs, teams, and working tested software and discusses governance structures with portfolio, program, and delivery teams.
More Related Content
Similar to Agile Transformation v1.27
![Rick Austin - Portfolio mangement in an agile world [Agile DC]](https://cdn.slidesharecdn.com/ss_thumbnails/portfoliomangementinanagileworld-agiledc-181015223517-thumbnail.jpg?width=640&height=640&fit=bounds)
Agile Transformation v1.27
- 3. THIS TALK ISABOUT GETTING PEOPLE TO MOVE...
- 4. AND KEEPING THEM MOVING THISTALK IS ABOUT GETTING PEOPLE TO MOVE...
- 16. G O AL S O F G O I N G A G I L E
- 17. G O AL S O F G O I N G A G I L E P R E D I C T A B I L I T Y Agile tends to focus on adaptability but predictability is most often cited as the reason for agile transformation
- 18. G O AL S O F G O I N G A G I L E Q U A L I T Y As organizations scale, product quality often suffers. Agile focuses on quality from requirements through implementation.
- 19. G O AL S O F G O I N G A G I L E E A R L Y R O I Many organizations struggle with 18 month delivery cycles. Agile helps your team accelerate time to market value
- 20. G O AL S O F G O I N G A G I L E L O W E R C O S T S Cost savings are tough to promise, but agile can help make sure you are spending money on features most likely to generate revenue
- 21. G O AL S O F G O I N G A G I L E I N N O V A T I O N As companies grow sometimes they slow down and loose the ability to innovate. Agile can help you get back your competitive edge.
- 22. G O AL S O F G O I N G A G I L E P R O D U C T F I T Delivering on time is only important if you are delivering the right product. Agile can help you get the feedback you need.
- 25. ... all threeare essential, but where you start is also essential…
- 26. H O WB I G I S T H E O R G A N I Z A T I O N ? Single Team Multiple Teams
- 27. D O TE A M S H A V E D E P E N D E N C I E S ? Non-instantly Available Resources Too Much Work in Process Large Products with Diverse Technology Low Cohesion & Tight Coupling Technical Debt & Defects Shared Requirements Between Teams Limited Access to Subject Matter Expertise Matrixed Organizations
- 28. H O WM U C H R E S I S T A N C E ?
- 30. T H E3 T H I N G S
- 31. T H E3 T H I N G S BACKLOGS
- 32. T H E3 T H I N G S BACKLOGS TEAMS
- 33. T H E3 T H I N G S BACKLOGS TEAMS WORKING TESTED SOFTWARE
- 34. W H AT D O I M E A N ? INVEST CCC Small enough for the team to develop in a day or so BACKLOGS TEAMS WORKING TESTED SOFTWARE Everything and everyone necessary to deliver Meets acceptance criteria No known defects No technical debt
- 35. INVEST CCC Small enough forthe team to develop in a day or so BACKLOGS TEAMS Everything and everyone necessary to deliver Meets acceptance criteria No known defects No technical debt W H A T D O I M E A N ? WORKING TESTED SOFTWARE
- 36. W H AT D O I M E A N ? INVEST CCC Small enough for the team to develop in a day or so BACKLOGS TEAMS Everything and everyone necessary to deliver Meets acceptance criteria No known defects No technical debt WORKING TESTED SOFTWARE
- 37. W H AT D O I M E A N ? Investment Decisioning Prioritization GOVERNANCE STRUCTURE METRICS Teaming Strategies at all levels of the organization How do we measure progress across teams How do we hold people accountable
- 38. W H AT D O I M E A N ? Investment Decisioning Prioritization GOVERNANCE STRUCTURE METRICS Teaming Strategies at all levels of the organization How do we measure progress across teams How do we hold people accountable
- 39. W H AT D O I M E A N ? Investment Decisioning Prioritization GOVERNANCE STRUCTURE METRICS Teaming Strategies at all levels of the organization How do we measure progress across teams How do we hold people accountable
- 40. W H ERE A R E W E NO W ?
- 41.
- 42.
- 43.
- 44.
- 45.
- 46.
- 47.
- 48.
- 49. T R ANS F O R M A T I O N I S A J O U RNEY
- 50.
- 51.
- 52.
- 53.
- 54.
- 55.
- 56. AE AC PE PC EMERGENCE CONVERGENCE ADAPTABILITY PREDICTABILITY AD-HOC LEAN STARTUP AGILELEAN/ AGILE LOW TRUST FULLYDECOUPLE REDUCE BATCH SIZEBECOME PREDICTABLE
- 57. A T HEO RY O F T R A NS F O R M A T I O N
- 58. THEORY OF TRANSFORMATION// Adopting agile is about forming teams, building backlogs, and regularly producing increments of working tested software
- 59. THEORY OF TRANSFORMATION// Adopting agile at scale is about defining structure, establishing governance, and creating a metrics and tooling strategy that supports agility
- 60. THEORY OF TRANSFORMATION// Anything that gets in the way of forming teams, building backlogs, and producing working tested software is an impediment to transformation
- 61. THEORY OF TRANSFORMATION// Solid agile practices will help operationalize the system and encourage a healthy, adaptive, and empowered culture emerge over time
- 62. W H ERE A R E W E G O I N G ?
- 63.
- 64. Gartner Mode Two Gartner Mode One AE AC PE PC EMERGENCE CONVERGENCE ADAPTABILITY PREDICTABILITY AD-HOCLEAN STARTUP AGILETRADITIONAL
- 65. M A PP I N G T H E J O U R NEY
- 66. AE AC PE PC EMERGENCE CONVERGENCE ADAPTABILITY PREDICTABILITY AD-HOC LEAN STARTUP AGILELEAN/ AGILE LOW TRUST FULLYDECOUPLE REDUCE BATCH SIZEBECOME PREDICTABLE T E A M S
- 67. BASECAMP 1 AE AC PE PC EMERGENCE CONVERGENCE ADAPTABILITY PREDICTABILITY AD-HOC LEAN STARTUP AGILELEAN/ AGILE LOWTRUST FULLY DECOUPLE REDUCE BATCH SIZEBECOME PREDICTABLE T E A M S B1
- 68. BASECAMP 2 AE AC PE PC EMERGENCE CONVERGENCE ADAPTABILITY PREDICTABILITY AD-HOC LEAN STARTUP AGILELEAN/ AGILE LOWTRUST FULLY DECOUPLE REDUCE BATCH SIZEBECOME PREDICTABLE T E A M S B1 B2
- 69. BASECAMP 3 AE AC PE PC EMERGENCE CONVERGENCE ADAPTABILITY PREDICTABILITY AD-HOC LEAN STARTUP AGILELEAN/ AGILE LOWTRUST FULLY DECOUPLE REDUCE BATCH SIZEBECOME PREDICTABLE T E A M S B1 B2 B3
- 70. BASECAMP 3 DevOps AE AC PE PC EMERGENCE CONVERGENCE ADAPTABILITY PREDICTABILITY AD-HOC LEAN STARTUP AGILELEAN/ AGILE LOWTRUST FULLY DECOUPLE REDUCE BATCH SIZEBECOME PREDICTABLE T E A M S B1 B2 B3
- 71. AE AC PE PC EMERGENCE CONVERGENCE ADAPTABILITY PREDICTABILITY AD-HOC LEAN STARTUP AGILELEAN/ AGILE LOW TRUST FULLYDECOUPLE REDUCE BATCH SIZEBECOME PREDICTABLE T E A M S B1 B2 B3 B4 BASECAMP 4
- 72. AE AC PE PC EMERGENCE CONVERGENCE ADAPTABILITY PREDICTABILITY AD-HOC LEAN STARTUP AGILELEAN/ AGILE LOW TRUST FULLYDECOUPLE REDUCE BATCH SIZEBECOME PREDICTABLE BASECAMP 5 T E A M S B1 B2 B3 B4 B5
- 74. Services Teams –These teams support common services across product lines. These teams support the needs of the product teams.
- 75. Product Teams –These teams integrate services and write customer facing features. This is the proto-typical Scrum team. Services Teams – These teams support common services across product lines. These teams support the needs of the product teams.
- 76. Programs Teams –These teams define requirements, set technical direction, and provide context and coordination. Product Teams – These teams integrate services and write customer facing features. This is the proto-typical Scrum team. Services Teams – These teams support common services across product lines. These teams support the needs of the product teams.
- 77. Portfolio Teams –These teams govern the portfolio and make sure that work is moving through the system. Programs Teams – These teams define requirements, set technical direction, and provide context and coordination. Product Teams – These teams integrate services and write customer facing features. This is the proto-typical Scrum team. Services Teams – These teams support common services across product lines. These teams support the needs of the product teams.
- 78.
- 79.
- 80.
- 81. G O VE R N A N C E
- 82. 3 - TI E R G O V E R N A N C E EPIC ALIGNMENT MAKE READY EPIC PRIORITIZATION FEATURE DEFINITION STORY READY SOLUTION VALIDATION RELEASE TARGETING STORY MAPPING RELEASE PLANNING IN PROGRESS IN PROGRESS IN PROGRESS EPIC VALIDATION INTEGRATION VALIDATION STORY DONE STORY ACCEPTED FEATURE DEVELOPMENT FEATURE COMPLETED COMPLETED PORTFOLIO TEAM PROGRAM TEAM DELIVERY TEAM STRATEGIC ALIGNMENT SOLUTION VISION DEMAND PLANNING EXECUTION VALIDATION ACCEPTED DEMAND PLANNING EXECUTION & ACCOUNTABILITY INTAKE E p i c | K a n b a n F e a t u r e | K a n b a n S t o r y | S c r u m
- 83. 4 - TI E R G O V E R N A N C E MAKE READY STORY READY IN PROGRESS STORY DONE STORY ACCEPTED EPIC ALIGNMENT EPIC PRIORITIZATION SOLUTION VALIDATION RELEASE TARGETING IN PROGRESS EPIC VALIDATION COMPLETED PORTFOLIO TEAM PROGRAM TEAM DELIVERY TEAM STRATEGIC ALIGNMENT SOLUTION VISION DEMAND PLANNING EXECUTION VALIDATION ACCEPTED DEMAND PLANNING EXECUTION & ACCOUNTABILITY FEATURE DEFINITION STORY MAPPING RELEASE PLANNING IN PROGRESS INTEGRATION VALIDATION FEATURE DEPLOYMENT FEATURE COMPLETED INTAKE INVESTMENT DECISION INVESTMENT TARGETING IN PROGRESS INITIATIVE VALIDATION COMPLETED INITIATIVE DEFINITION INITIATIVE ROADMAP MEASUREABLE PROGRESS INVESTMENT I n i t i a t i v e | K a n b a n E p i c | K a n b a n F e a t u r e | K a n b a n S t o r y | S c r u m
- 84. M E TR I C S
- 85.
- 86. Scrum Kanban Kanban Backlog Size Velocity Burndown Escaped Defects Commit% Acceptance % Ratio Scope Change PORTFOLIO TEAMS DELIVERY TEAMS PROGRAM TEAMS
- 87. Scrum Kanban Kanban Backlog Size Velocity Burndown Escaped Defects Commit% Acceptance % Ratio Scope Change Cycle Time Features Blocked Rework/Defects PORTFOLIO TEAMS DELIVERY TEAMS PROGRAM TEAMS
- 88. Scrum Kanban Kanban Backlog Size Velocity Burndown Escaped Defects Commit% Acceptance % Ratio Scope Change Cycle Time Features Blocked Rework/Defects Takt Time/ Cycle Time Time/Cost/Scope/Value ROI/Capitalization PORTFOLIO TEAMS DELIVERY TEAMS PROGRAM TEAMS
- 90. I NC REMENT A L T R A NS F O R M A T I O N ( EX P ED I T I O NS )
- 91.
- 92. PROGRAM TEAMS PORTFOLIO TEAMS DELIVERY TEAMS Scr um Kanban Kanban AGILE PILOT ExpeditionOne AGILE ROLLOUT Expedition Two
- 93. PROGRAM TEAMS PORTFOLIO TEAMS DELIVERY TEAMS Scr um Kanban Kanban AGILE PILOT ExpeditionOne AGILE ROLLOUT Expedition Three ➔ N
- 94. I T ERAT I V E T R A NS F O R M A T I O N ( BA S EC A M P S )
- 95.
- 96.
- 97.
- 98.
- 99.
- 100. EX P EDI T I O NS & BA S EC A M P S
- 101.
- 102.
- 103. PROGRAM TEAMS PORTFOLIO TEAMS DELIVERY TEAMS Scr um Kanban Kanban AGILE PILOT BasecampThree AGILE ROLLOUT Basecamp One
- 104. PROGRAM TEAMS PORTFOLIO TEAMS DELIVERY TEAMS Scr um Kanban Kanban AGILE PILOT BasecampFour AGILE ROLLOUT Basecamp Two
- 105. PROGRAM TEAMS PORTFOLIO TEAMS DELIVERY TEAMS Scr um Kanban Kanban AGILE PILOT BasecampFive AGILE ROLLOUT Basecamp Three
- 106. P L AYBO O K & F I EL D G U I D E
- 107. S T EP 1 Agile transformation isn’t something that can be done to an organization. They have to be full participants Holding the organization accountable Remove Impediments Plan the work Review Progress Inspect and Adapt WHY WHAT HOW Executive Steering Committee Transformation Leadership Team
- 108. S T EP 2 We have to have some idea of where we are going before we start We will accept the plan will change Transformation Workshop Pilot Broad Organization Rollout Create Feedback Loops WHY WHAT HOW Create a working hypothesis for structure, governance, and metrics Plan to progressively elaborate
- 109. S T EP 3 We have to be able to give the organization some idea of what we are doing, when, and how long What teams are going to be formed? What training do they need? What coaching do they need? When will this all happen? WHY WHAT HOW Expeditions Basecamps Sequenced in Time
- 110. S T EP 4 Very similar to an agile release plan, we want a rolling 90 day, fairly specific view of what is going to take place Week by week training and coaching plans Detailed resource planning Expected activities and outcomes. WHY WHAT HOW Transformation leadership team meets periodically to plan forward, assess progress, and adjust as necessary
- 111. S T EP 5 Very similar to a sprint cycle in Scrum We want to periodically assess progress, retrospect, and adjust Scheduled recurring meetings Review planning artifacts Review metrics Improvement plans WHY WHAT HOW ELT reviews progress against strategy and outcomes TLT focuses on how well the plan is moving along
- 112. S T EP 6 The whole reason we are doing this is to get better business outcomes This is where we begin justifying the investment Assessments Status Reports Coaching Plans WHY WHAT HOW Create hypotheses Conduct experiments Demonstrate outcomes Pivot based on what we learn
- 113. S T EP 7 We want to be able to trace improvements in the system to tangible business benefits Assessment Outcomes Transformation metrics Business Metrics WHY WHAT HOW Business metric baselines Regularly show progress Update coaching plans as necessary
- 114. S T EP 8 Our understanding will evolve throughout the transformation Refine the End- State Vision and the Roadmap WHY WHAT HOW Re-assess the End- State Vision based on the evolving understanding
- 115. S T EP 9 Letting everyone know what is going on and the success of the program will create excitement and energy Town Halls Executive roundtables Signage Information Radiators Cadence of Accountability WHY WHAT HOW Regular communication from leadership Be transparent about progress and impediments
- 116. S T EP 1 0 Understand what’s in it for everyone involved and help them see where they fit in the new organization Team assignments Staffing plans Job descriptions Job aids Communities of Practice WHY WHAT HOW Clarity Accountability Measurable progress
- 118. T R ANS F O R M A T I O N M E T R I C S
- 119. C A PA B I L I T Y I M P R O V E M E N T S
- 120. C A PA B I L I T Y I M P R O V E M E N T S DEFINE THE PRODUCT
- 121. PLAN & COORDINATE CA P A B I L I T Y I M P R O V E M E N T S DEFINE THE PRODUCT
- 122. PLAN & COORDINATE CA P A B I L I T Y I M P R O V E M E N T S DEFINE THE PRODUCT DELIVER THE SOLUTION
- 123. ORGANIZATION ENABLEMENT PLAN &COORDINATE C A P A B I L I T Y I M P R O V E M E N T S DEFINE THE PRODUCT DELIVER THE SOLUTION
- 124. ORGANIZATION ENABLEMENT PLAN &COORDINATE C A P A B I L I T Y I M P R O V E M E N T S DEFINE THE PRODUCT DELIVER THE SOLUTION CONTINUOUS IMPROVEMENT
- 125. M E AS U R I N G P R O G R E S S
- 126. M E AS U R I N G P R O G R E S S ACTIVITIE S
- 127. M E AS U R I N G P R O G R E S S ACTIVITIE S OUTCOME S
- 128. M E AS U R I N G P R O G R E S S ACTIVITIE S OUTCOME S B ASE CAMPS
- 129. BU S INES S M E T R I C S
- 130. G O AL S A N D O B J E C T I V E S
- 131. G O AL S A N D O B J E C T I V E S PREDICTABILITY
- 132. G O AL S A N D O B J E C T I V E S PREDICTABILITY QUALITY
- 133. G O AL S A N D O B J E C T I V E S PREDICTABILITY EARLY ROI QUALITY
- 134. G O AL S A N D O B J E C T I V E S PREDICTABILITY EARLY ROI QUALITY LOWER COSTS
- 135. G O AL S A N D O B J E C T I V E S PREDICTABILITY EARLY ROI INNOVATION QUALITY LOWER COSTS
- 136. G O AL S A N D O B J E C T I V E S PREDICTABILITY EARLY ROI INNOVATION QUALITY LOWER COSTS PRODUCT FIT
- 137. F I NA N C I A L M E A S U R E M E N T
- 138. F I NA N C I A L M E A S U R E M E N T RETURN ON INVESTMENT
- 139. F I NA N C I A L M E A S U R E M E N T RETURN ON INVESTMENT PAYBACK PERIOD
- 140. F I NA N C I A L M E A S U R E M E N T RETURN ON INVESTMENT PAYBACK PERIOD CAPITALIZATION RATE
- 141. F I NA N C I A L M E A S U R E M E N T RETURN ON INVESTMENT PAYBACK PERIOD CAPITALIZATION RATE REVENUE ACCELERATION
- 142. F I NA N C I A L M E A S U R E M E N T RETURN ON INVESTMENT PAYBACK PERIOD CAPITALIZATION RATE REVENUE ACCELERATION PRODUCTIVITY IMPROVEMENTS
- 143. F I NA N C I A L M E A S U R E M E N T RETURN ON INVESTMENT PAYBACK PERIOD CAPITALIZATION RATE REVENUE ACCELERATION PRODUCTIVITY IMPROVEMENTS EMPLOYEE TURNOVER RATIO
- 145. R O LE S
- 146. R O LE S ACCOUNT LEAD
- 147. R O LE S TRANSFORMATION LEAD ACCOUNT LEAD
- 148. R O LE S TRANSFORMATION LEAD EXPEDITION LEAD ACCOUNT LEAD
- 149. R O LE S TRANSFORMATION LEAD EXPEDITION LEAD ENTERPRISE TRANSFORMATION CONSULTANT ACCOUNT LEAD
- 150. R O LE S TRANSFORMATION LEAD EXPEDITION LEAD ENTERPRISE TRANSFORMATION CONSULTANT ANALYST ACCOUNT LEAD
- 151. R O LE S TRANSFORMATION LEAD EXPEDITION LEAD ENTERPRISE TRANSFORMATION CONSULTANT ANALYST SPECIALIST ACCOUNT LEAD
- 153. C O MP E T E N C I E S
- 154. C O MP E T E N C I E S Skills Experience Culture Community
- 155. C O MP E T E N C I E S Skills Experience Culture Community Beliefs Behaviors
- 156. C O MP E T E N C I E S Skills Experience Culture Community Beliefs Behaviors EQ IQ
- 157. C O MP E T E N C I E S Skills Experience Culture Community Beliefs Behaviors EQ IQ Pattern Recognition Systems Thinking
- 158. T I TL E S
- 159.
- 160.
- 161.
- 162. ASSOCIATE CONSULTANT STAFF CONSULTANT SENIOR CONSULTANT T I TL E S MANAGING CONSULTANT
- 163. ASSOCIATE CONSULTANT STAFF CONSULTANT SENIOR CONSULTANT T I TL E S MANAGING CONSULTANT PRINCIPLE CONSULTANT
- 164.