Can Change Management Support Agile Without Being Agile?

Size: px
Start display at page:

Download "Can Change Management Support Agile Without Being Agile?"

Transcription

1 Can Change Management Support Agile Without Being Agile? Eric J Hansen

2 Agenda How Big is The Highway? Frontage Roads Support the Highway Travel Tips (Best Practices)

3 How Big is The Highway? Where Are The Changes in Agile? Provide Comprehensive Support to All Changes All Epics Are Not Created Equal: Creating Differentiation

4 Where Are The Changes in Agile? Strategic Themes / Epics / Portfolio Agile Release Trains / Solutions / Features

5 Provide Comprehensive Support Find the Change, Apply a Framework Manage All Changes - Collectively & Individually

6 Creating Differentiation Factors to score for change management impact ( ) : Structure: Organizational span of the change - horizontal, integration, complexity Systems & Tools: How is the technology changing? Talent (Leadership): Change capability of leaders and employees required for success Processes: How work flows Culture, Values & Attitudes: Organizational health, resilience Strategy: Gaps in strategic or leader alignment Behaviors: Degree of behavioral changes between current and future state Knowledge, Skills, & Abilities: New capabilities and capacities needed

7 Creating Differentiation: You Try Table Exercise: Create Your Own Differentiation Model What differentiators have you / would you use? How would you measure / score them?

8 Creating Differentiation: You Try Dimension Name Measurement

9 Frontage Roads Support the Highway Identify the Entrance Ramps & Exits Common Language is Like Signage

10 Identify the Entrance Ramps & Exits Align/integrate change & Agile deliverables like highway ramps AGILE PORTFOLIO Business Case Defined CHANGE DELIVERABLES Description Success criteria ID Key stakeholders Personna(s) Business Risk Definitions / Assessment Change Impact Analysis Product Road Map Go/No Go Decision (Start Stop Continue) Define Current State Define Future State Product Backlog Dependencies Identification Minimum Viable Product (MVP) Define the case for change Document vision alignment Identify the goals, objectives, and success criteria for the future state Document the current state Identify and document impacted stakeholders Assess change impact (gap between CS & FS, other changes) Assess sponsorship and alignment Perform organizational change readiness assessments Document resistance and risk sources Create the change strategy and plan Communicate key messages and learning opportunities Incorporate change deliverables into backlog * BEST PRACTICE: Just as you often get onto and off the highway (to get gas, stop and eat, sightsee, etc), iterate your change planning and execution

11 Common Language is Like Signage TABLE EXERCISE: Discuss and create a list of potential exit criteria for some change deliverables * BEST PRACTICE: Create change related exit criteria for epics and planning iterations

12 Exit Criteria for Change Deliverables STRATEGIC THEME / EPICS / ARTs PLANNING ITERATIONS CHANGE DELIVERBALES

13 Travel Tips (Best Practices) Thoughts From Seasoned Travelers (Group Discussion) Differentiate by impact Iterate your change planning and execution Create change related Exit criteria for epics and planning iterations (especially communication) Cascading change deliverables: portfolios inform programs, which inform programs, which inform features Iterative execution

14 Thank you!