Transcript
Page 1: Agile transformation Explained: Agile 2017 Session

A G I L E T R A N S F O R M A T I O N

Page 2: Agile transformation Explained: Agile 2017 Session

22

[email protected]

404-312-1471

www.leadingagile.com

twitter.com/mcottmeyer

facebook.com/leadingagile

linkedin.com/in/cottmeyer

MIKE COTTMEYER

Page 3: Agile transformation Explained: Agile 2017 Session

33

• Deciding the Scope of the Transformation

• Deciding Your Transformation Approach

• Managing Change and Measuring Progress

BRIEF AGENDA

Page 4: Agile transformation Explained: Agile 2017 Session

44

• Deciding the Scope of the Transformation

• Deciding Your Transformation Approach

• Managing Change and Measuring Progress

BRIEF AGENDA

Page 5: Agile transformation Explained: Agile 2017 Session

55

• Deciding the Scope of the Transformation

• Deciding Your Transformation Approach

• Managing Change and Measuring Progress

BRIEF AGENDA

Page 6: Agile transformation Explained: Agile 2017 Session

66

• Deciding the Scope of the Transformation

• Deciding Your Transformation Approach

• Managing Change and Measuring Progress

BRIEF AGENDA

Page 7: Agile transformation Explained: Agile 2017 Session

DECIDING THE SCOPE OF THE TRANSFORMATION

Page 8: Agile transformation Explained: Agile 2017 Session

W H Y A R E W E T R A N S F O R M I N G ?

Page 9: Agile transformation Explained: Agile 2017 Session

99

GOALS OF GOING AGILE

PREDICTABILITY

Agile tends to focus on adaptability but

predictability is most often cited as the reason

for agile transformation

EARLY ROI

Many organizations struggle with 18 month

delivery cycles. Agile helps your team

accelerate time to market value

INNOVATION

As companies grow sometimes they slow down

and loose th ability to innovate. Agile can help

you get back your competitive edge.

QUALITY

As organizations scale, product quality often

suffers. Agile focuses on quality from

requirements through implementation.

LOWER COSTS

Cost savings are tough to promise, but agile can

help make sure you are only spending money

on the features most likely to generate revenue

PRODUCT FIT

Delivering on time is only important if you are

delivering the right product. Agile can help you

get the feedback you need.

Page 10: Agile transformation Explained: Agile 2017 Session

W H A T A R E W ET R A N S F O R M I N G ?

Page 11: Agile transformation Explained: Agile 2017 Session

1111

Page 12: Agile transformation Explained: Agile 2017 Session

1212

CULTURE FOCUSED

Focused on changing hearts and minds

Focused on being agile rather than doing agile

Focused on values and principles

Page 13: Agile transformation Explained: Agile 2017 Session

1313

CULTURE FOCUSED

Focused on changing hearts and minds

Focused on being agile rather than doing agile

Focused on values and principles

Belief that delivery systems will emerge based on new thinking

Page 14: Agile transformation Explained: Agile 2017 Session

1414

PRACTICES FOCUSED

Focused on the things that you do

Focused on roles, ceremonies, and artifacts

Can be management driven or technically driven

Page 15: Agile transformation Explained: Agile 2017 Session

1515

PRACTICES FOCUSED

Focused on the things that you do

Focused on roles, ceremonies, and artifacts

Can be management driven or technically driven

Belief that agile is a process or way to work

Page 16: Agile transformation Explained: Agile 2017 Session

1616

SYSTEMS FOCUSED

Focused on forming teams and governing the flow of value

Focused on aligning the organization first

Page 17: Agile transformation Explained: Agile 2017 Session

1717

SYSTEMS FOCUSED

Focused on forming teams and governing the flow of value

Focused on aligning the organization first

Belief that culture and practices only emerge within a rational structural and planning framework

Page 18: Agile transformation Explained: Agile 2017 Session

1818

... all three are essential, but where you start is also essential…

Page 19: Agile transformation Explained: Agile 2017 Session

W H A T D O W E N E E D T O O V E R C O M E ?

Page 20: Agile transformation Explained: Agile 2017 Session

2020

HOW BIG IS THE ORGANIZATION?

Single Team

Multiple Teams

Page 21: Agile transformation Explained: Agile 2017 Session

2121

DO TEAMS HAVE DEPENDENCIES?

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

Page 22: Agile transformation Explained: Agile 2017 Session

2222

HOW MUCH RESISTANCE?

Page 23: Agile transformation Explained: Agile 2017 Session

DEFINING A TRANSFORMATION APPROACH

Page 24: Agile transformation Explained: Agile 2017 Session

T H E N O N -N E G O T I A B L E C O R E

Page 25: Agile transformation Explained: Agile 2017 Session

2525

THE 3 THINGS

Page 26: Agile transformation Explained: Agile 2017 Session

2626

BACKLOGS

THE 3 THINGS

Page 27: Agile transformation Explained: Agile 2017 Session

2727

BACKLOGS TEAMS

THE 3 THINGS

Page 28: Agile transformation Explained: Agile 2017 Session

2828

BACKLOGS TEAMS WORKING TESTED SOFTWARE

THE 3 THINGS

Page 29: Agile transformation Explained: Agile 2017 Session

2929

WHAT DO I MEAN?

• 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

Page 30: Agile transformation Explained: Agile 2017 Session

3030

WHAT DO I MEAN?

• 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

Page 31: Agile transformation Explained: Agile 2017 Session

3131

WHAT DO I MEAN?

• 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

Page 32: Agile transformation Explained: Agile 2017 Session

3232

WHY ARE THEY IMPORTANT?

• People have clarity around what to build

• People understand how it maps to the big picture

CLARITY ACCOUNTABILITY MEASURABLE PROGRESS

• Teams can be held accountable for delivery

• No indeterminate work piling up at the end of the project

• 90% done, 90% left to do

Page 33: Agile transformation Explained: Agile 2017 Session

3333

WHY ARE THEY IMPORTANT?

• People have clarity around what to build

• People understand how it maps to the big picture

CLARITY ACCOUNTABILITY MEASURABLE PROGRESS

• Teams can be held accountable for delivery

• No indeterminate work piling up at the end of the project

• 90% done, 90% left to do

Page 34: Agile transformation Explained: Agile 2017 Session

3434

WHY ARE THEY IMPORTANT?

• People have clarity around what to build

• People understand how it maps to the big picture

CLARITY ACCOUNTABILITY MEASURABLE PROGRESS

• Teams can be held accountable for delivery

• No indeterminate work piling up at the end of the project

• 90% done, 90% left to do

Page 35: Agile transformation Explained: Agile 2017 Session

3535

WHY ARE THEY IMPORTANT?

• Understanding the backlog gives meaning to work

PURPOSE AUTONOMY MASTERY

• Local decision making gives people a sense of power and control over their work

• People can demonstrate that they are good at what they do

Page 36: Agile transformation Explained: Agile 2017 Session

3636

WHY ARE THEY IMPORTANT?

• Understanding the backlog gives meaning to work

PURPOSE AUTONOMY MASTERY

• Local decision making gives people a sense of power and control over their work

• People can demonstrate that they are good at what they do

Page 37: Agile transformation Explained: Agile 2017 Session

3737

WHY ARE THEY IMPORTANT?

• Understanding the backlog gives meaning to work

PURPOSE AUTONOMY MASTERY

• Local decision making gives people a sense of power and control over their work

• People can demonstrate that they are good at what they do

Page 38: Agile transformation Explained: Agile 2017 Session

E L E M E N T S O F O R G A N I Z A T I O N

Page 39: Agile transformation Explained: Agile 2017 Session

3939

Services Teams – These teams support common services across product lines. These teams support the needs of the product teams.

Page 40: Agile transformation Explained: Agile 2017 Session

4040

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.

Page 41: Agile transformation Explained: Agile 2017 Session

4141

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.

Page 42: Agile transformation Explained: Agile 2017 Session

4242

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.

Page 43: Agile transformation Explained: Agile 2017 Session

4343

DELIVERY TEAMS

Page 44: Agile transformation Explained: Agile 2017 Session

4444

PROGRAM TEAMS

DELIVERY TEAMS

Page 45: Agile transformation Explained: Agile 2017 Session

4545

PROGRAM TEAMS

PORTFOLIO TEAMS

DELIVERY TEAMS

Page 46: Agile transformation Explained: Agile 2017 Session

W H E R E A R E W E ?

Page 47: Agile transformation Explained: Agile 2017 Session

4747

AD

APTA

BILITYPR

EDIC

TABI

LITY

Page 48: Agile transformation Explained: Agile 2017 Session

4848

EMERGENCE

CONVERGENCE

AD

APTA

BILITYPR

EDIC

TABI

LITY

Page 49: Agile transformation Explained: Agile 2017 Session

4949

AE

PC

EMERGENCE

CONVERGENCE

AD

APTA

BILITYPR

EDIC

TABI

LITY

Page 50: Agile transformation Explained: Agile 2017 Session

5050

AE

AC

PE

PC

EMERGENCE

CONVERGENCE

AD

APTA

BILITYPR

EDIC

TABI

LITY

Page 51: Agile transformation Explained: Agile 2017 Session

5151

AE

AC

PE

PC

EMERGENCE

CONVERGENCE

AD

APTA

BILITYPR

EDIC

TABI

LITY

AD-HOC LEANSTARTUP

AGILETRADITIONAL

Q U A D R A N T 1

Page 52: Agile transformation Explained: Agile 2017 Session

5252

AE

AC

PE

PC

EMERGENCE

CONVERGENCE

AD

APTA

BILITYPR

EDIC

TABI

LITY

AD-HOC LEANSTARTUP

AGILETRADITIONAL

Q U A D R A N T 2

Page 53: Agile transformation Explained: Agile 2017 Session

5353

AE

AC

PE

PC

EMERGENCE

CONVERGENCE

AD

APTA

BILITYPR

EDIC

TABI

LITY

AD-HOC LEANSTARTUP

AGILETRADITIONAL

Q U A D R A N T 3

Page 54: Agile transformation Explained: Agile 2017 Session

5454

AE

AC

PE

PC

EMERGENCE

CONVERGENCE

AD

APTA

BILITYPR

EDIC

TABI

LITY

AD-HOC LEANSTARTUP

AGILETRADITIONAL

Q U A D R A N T 4

Page 55: Agile transformation Explained: Agile 2017 Session

A T H E O R Y O F T R A N S F O R M A T I O N

Page 56: Agile transformation Explained: Agile 2017 Session

T H E O R Y O F T R A N S F O R M A T I O N / /

Adopting agile is about forming

teams, building backlogs, and

regularly producing increments

of working tested software

Page 57: Agile transformation Explained: Agile 2017 Session

T H E O R Y O F T R A N S F O R M A T I O N / /

Adopting agile at scale is about

defining structure, establishing

governance, and creating a

metrics and tooling strategy

that supports agility

Page 58: Agile transformation Explained: Agile 2017 Session

T H E O R Y O F T R A N S F O R M A T I O N / /

Anything that gets in the way

of forming teams, building

backlogs, and producing

working tested software is an

impediment to transformation

Page 59: Agile transformation Explained: Agile 2017 Session

T H E O R Y O F T R A N S F O R M A T I O N / /

Solid agile practices will help

operationalize the system and

encourage a healthy, adaptive,

and empowered culture

emerges over time

Page 60: Agile transformation Explained: Agile 2017 Session

T R A N S F O R M A T I O NI S A J O U R N E Y

Page 61: Agile transformation Explained: Agile 2017 Session

6161

AE

AC

PE

PC

EMERGENCE

CONVERGENCE

AD

APTA

BILITYPR

EDIC

TABI

LITY

AD-HOC LEANSTARTUP

AGILETRADITIONAL

Page 62: Agile transformation Explained: Agile 2017 Session

6262

AE

AC

PE

PC

EMERGENCE

CONVERGENCE

AD

APTA

BILITYPR

EDIC

TABI

LITY

AD-HOC LEANSTARTUP

AGILETRADITIONAL

LOW TRUST

Page 63: Agile transformation Explained: Agile 2017 Session

6363

AE

AC

PE

PC

EMERGENCE

CONVERGENCE

AD

APTA

BILITYPR

EDIC

TABI

LITY

AD-HOC LEANSTARTUP

AGILETRADITIONAL

LOW TRUST

BECOME PREDICTABLE

Page 64: Agile transformation Explained: Agile 2017 Session

6464

AE

AC

PE

PC

EMERGENCE

CONVERGENCE

AD

APTA

BILITYPR

EDIC

TABI

LITY

AD-HOC LEANSTARTUP

AGILETRADITIONAL

LOW TRUST

BECOME PREDICTABLE

Page 65: Agile transformation Explained: Agile 2017 Session

6565

AE

AC

PE

PC

EMERGENCE

CONVERGENCE

AD

APTA

BILITYPR

EDIC

TABI

LITY

AD-HOC LEANSTARTUP

AGILELEAN/AGILE

LOW TRUST

BECOME PREDICTABLE

Page 66: Agile transformation Explained: Agile 2017 Session

6666

AE

AC

PE

PC

EMERGENCE

CONVERGENCE

AD

APTA

BILITYPR

EDIC

TABI

LITY

AD-HOC LEANSTARTUP

AGILELEAN/AGILE

LOW TRUST

REDUCE BATCH SIZEBECOME PREDICTABLE

Page 67: Agile transformation Explained: Agile 2017 Session

6767

AE

AC

PE

PC

EMERGENCE

CONVERGENCE

AD

APTA

BILITYPR

EDIC

TABI

LITY

AD-HOC LEANSTARTUP

AGILELEAN/AGILE

LOW TRUSTFULLY DECOUPLE

REDUCE BATCH SIZEBECOME PREDICTABLE

Page 68: Agile transformation Explained: Agile 2017 Session

6868

AE

AC

PE

PC

EMERGENCE

CONVERGENCE

AD

APTA

BILITYPR

EDIC

TABI

LITY

AD-HOC LEANSTARTUP

AGILELEAN/AGILE

LOW TRUSTFULLY DECOUPLE

REDUCE BATCH SIZEBECOME PREDICTABLE

T E A M S

Page 69: Agile transformation Explained: Agile 2017 Session

6969

AE

AC

PE

PC

EMERGENCE

CONVERGENCE

AD

APTA

BILITYPR

EDIC

TABI

LITY

P H A S E 1AD-HOC LEAN

STARTUP

AGILELEAN/AGILE

LOW TRUSTFULLY DECOUPLE

REDUCE BATCH SIZEBECOME PREDICTABLE

T E A M S

P1

Page 70: Agile transformation Explained: Agile 2017 Session

7070

AE

AC

PE

PC

EMERGENCE

CONVERGENCE

AD

APTA

BILITYPR

EDIC

TABI

LITY

P H A S E 2AD-HOC LEAN

STARTUP

AGILELEAN/AGILE

LOW TRUSTFULLY DECOUPLE

REDUCE BATCH SIZEBECOME PREDICTABLE

T E A M S

P1 P2

Page 71: Agile transformation Explained: Agile 2017 Session

7171

AE

AC

PE

PC

EMERGENCE

CONVERGENCE

AD

APTA

BILITYPR

EDIC

TABI

LITY

P H A S E 3AD-HOC LEAN

STARTUP

AGILELEAN/AGILE

LOW TRUSTFULLY DECOUPLE

REDUCE BATCH SIZEBECOME PREDICTABLE

T E A M S

P1 P2P3

Page 72: Agile transformation Explained: Agile 2017 Session

7272

AE

AC

PE

PC

EMERGENCE

CONVERGENCE

AD

APTA

BILITYPR

EDIC

TABI

LITY

P H A S E 4AD-HOC LEAN

STARTUP

AGILELEAN/AGILE

LOW TRUSTFULLY DECOUPLE

REDUCE BATCH SIZEBECOME PREDICTABLE

T E A M S

P1 P2P3

P4

Page 73: Agile transformation Explained: Agile 2017 Session

7373

AE

AC

PE

PC

EMERGENCE

CONVERGENCE

AD

APTA

BILITYPR

EDIC

TABI

LITY

P H A S E 5AD-HOC LEAN

STARTUP

AGILELEAN/AGILE

LOW TRUSTFULLY DECOUPLE

REDUCE BATCH SIZEBECOME PREDICTABLE

T E A M S

P1 P2P3

P4

P5

Page 74: Agile transformation Explained: Agile 2017 Session

W H E R E A R E W E G O I N G ?

Page 75: Agile transformation Explained: Agile 2017 Session

7575

METHODOLOGIES & FRAMEWORKS

Waterfall

Rational Unified Process (RUP)

DSDM

FDD

SAFe

DAD

LeSS

Nexus

Scrum

XP

Kanban

Crystal

Lean

Lean Startup

Page 76: Agile transformation Explained: Agile 2017 Session

7676

LEAN/AGILE

Waterfall

RUP

SAFeDSDM

FDD

DAD

Nexus

LeSS

ScrumXP

Crystal

LeanAE

AC

PE

PC

EMERGENCE

CONVERGENCE

AD

APTA

BILITYPR

EDIC

TABI

LITY

AD-HOC LEANSTARTUP

AGILE

Page 77: Agile transformation Explained: Agile 2017 Session

H O W D O W E G E T T H E R E ?

Page 78: Agile transformation Explained: Agile 2017 Session

7878

DELIVERY TEAMS

Sc r um

Page 79: Agile transformation Explained: Agile 2017 Session

7979

PROGRAM TEAMS

DELIVERY TEAMS

Sc r um

Kanb an

Page 80: Agile transformation Explained: Agile 2017 Session

8080

PROGRAM TEAMS

PORTFOLIO TEAMS

DELIVERY TEAMS

Sc r um

Kanb an

Kanb an

Page 81: Agile transformation Explained: Agile 2017 Session

I N C R E M E N T A LT R A N S F O R M A T I O N

( E X P E D I T I O N S )

Page 82: Agile transformation Explained: Agile 2017 Session

8282

PROGRAM TEAMS

PORTFOLIO TEAMS

DELIVERY TEAMS

Sc r um

Kanb an

Kanb an

AGILE PILOT

Increment One

Page 83: Agile transformation Explained: Agile 2017 Session

8383

PROGRAM TEAMS

PORTFOLIO TEAMS

DELIVERY TEAMS

Sc r um

Kanb an

Kanb an

AGILE PILOT

Increment One

AGILE ROLLOUT

Increment Two

Page 84: Agile transformation Explained: Agile 2017 Session

8484

PROGRAM TEAMS

PORTFOLIO TEAMS

DELIVERY TEAMS

Sc r um

Kanb an

Kanb an

AGILE PILOT

Increment One

AGILE ROLLOUT

Three - N

Page 85: Agile transformation Explained: Agile 2017 Session

I T E R A T I V ET R A N S F O R M A T I O N

( B A S E C A M P S )

Page 86: Agile transformation Explained: Agile 2017 Session

8686

PROGRAM TEAMS

PORTFOLIO TEAMS

DELIVERY TEAMS

Sc r um

Kanb an

Kanb an

AGILE PILOT

Iteration One

Page 87: Agile transformation Explained: Agile 2017 Session

8787

PROGRAM TEAMS

PORTFOLIO TEAMS

DELIVERY TEAMS

Sc r um

Kanb an

Kanb an

AGILE PILOT

Iteration Two

Page 88: Agile transformation Explained: Agile 2017 Session

8888

PROGRAM TEAMS

PORTFOLIO TEAMS

DELIVERY TEAMS

Sc r um

Kanb an

Kanb an

AGILE PILOT

Iteration Three

Page 89: Agile transformation Explained: Agile 2017 Session

8989

PROGRAM TEAMS

PORTFOLIO TEAMS

DELIVERY TEAMS

Sc r um

Kanb an

Kanb an

AGILE PILOT

Iteration Four

Page 90: Agile transformation Explained: Agile 2017 Session

9090

PROGRAM TEAMS

PORTFOLIO TEAMS

DELIVERY TEAMS

Sc r um

Kanb an

Kanb an

AGILE PILOT

Iteration Five

Page 91: Agile transformation Explained: Agile 2017 Session

E X P E D I T I O N S &B A S E C A M P S

Page 92: Agile transformation Explained: Agile 2017 Session

9292

PROGRAM TEAMS

PORTFOLIO TEAMS

DELIVERY TEAMS

Sc r um

Kanb an

Kanb an

AGILE PILOT

Iteration One

Page 93: Agile transformation Explained: Agile 2017 Session

9393

PROGRAM TEAMS

PORTFOLIO TEAMS

DELIVERY TEAMS

Sc r um

Kanb an

Kanb an

AGILE PILOT

Iteration Two

Page 94: Agile transformation Explained: Agile 2017 Session

9494

PROGRAM TEAMS

PORTFOLIO TEAMS

DELIVERY TEAMS

Sc r um

Kanb an

Kanb an

AGILE PILOT

Iteration Three

AGILE ROLLOUT

Iteration One

Page 95: Agile transformation Explained: Agile 2017 Session

9595

PROGRAM TEAMS

PORTFOLIO TEAMS

DELIVERY TEAMS

Sc r um

Kanb an

Kanb an

AGILE PILOT

Iteration Four

AGILE ROLLOUT

Iteration Two

Page 96: Agile transformation Explained: Agile 2017 Session

9696

PROGRAM TEAMS

PORTFOLIO TEAMS

DELIVERY TEAMS

Sc r um

Kanb an

Kanb an

AGILE PILOT

Iteration Five

AGILE ROLLOUT

Iteration Three

Page 97: Agile transformation Explained: Agile 2017 Session

MANAGING CHANGE AND MEASURING PROGRESS

Page 98: Agile transformation Explained: Agile 2017 Session

P L A N N I N G A N D E X E C U T I O N

Page 99: Agile transformation Explained: Agile 2017 Session

99

STEP ONE

W H Y H O W W H A T

Agile transformation isn’t something that can

be done to an organization.

They have to be full participants

Executive Steering Committee

Transformation Leadership Team

Holding the organization accountable

Remove Impediments

Plan the work

Review Progress

Inspect and Adapt

Page 100: Agile transformation Explained: Agile 2017 Session

100

STEP TWO

W H Y H O W W H A T

We have to have some idea of where we are going before we start

We will accept the plan will change

Create a working hypothesis for

structure, governance, and metrics

Plan to progressively elaborate

Transformation Workshop

Pilot

Broad Organization Rollout

Create Feedback Loops

Page 101: Agile transformation Explained: Agile 2017 Session

101

STEP THREE

W H Y H O W W H A T

We have to be able to give the organization some idea of what we are doing, when, and

how long

Expeditions

Basecamps

Sequenced in Time

What teams are going to be formed?

What training do they need?

What coaching do they need?

When will this all happen?

Page 102: Agile transformation Explained: Agile 2017 Session

102

STEP FOUR

W H Y H O W W H A T

Very similar to an agile release plan, we want a

rolling 90-day, fairly specific view of what is

going to take place

Transformation leadership team meets

periodically to plan forward, assess

progress, and adjust as necessary

Week by week training and coaching plans

Detailed resource planning

Expected activities and outcomes.

Page 103: Agile transformation Explained: Agile 2017 Session

103

STEP FIVE

W H Y H O W W H A T

Very similar to a sprint cycle in Scrum

We want to periodically assess

progress, retrospect, and adjust

ELT reviews progress against strategy and

outcomes

TLT focuses on how well the plan is moving

along

Scheduled recurring meetings

Review planning artifacts

Review metrics

Improvement plans

Page 104: Agile transformation Explained: Agile 2017 Session

104

STEP SIX

W H Y H O W W H A T

The whole reason we are doing this is to get

better business outcomes

This is where we begin justifying the

investment

Create hypotheses

Conduct experiments

Demonstrate outcomes

Pivot based on what we learn

Assessments

Status Reports

Coaching Plans

Page 105: Agile transformation Explained: Agile 2017 Session

105

STEP SEVEN

W H Y H O W W H A T

We want to be able to trace improvements in the system to tangible

business benefits

Business metric baselines

Regularly show progress

Update coaching plans as necessary

Assessment Outcomes

Transformation Metrics

Business Metrics

Page 106: Agile transformation Explained: Agile 2017 Session

106

STEP EIGHT

W H Y H O W W H A T

Our understanding will evolve throughout the

transformation

Re-assess the End-State Vision based on the

evolving understanding

Refine the End-State Vision and the

Roadmap

Page 107: Agile transformation Explained: Agile 2017 Session

107

STEP NINE

W H Y H O W W H A T

Letting everyone know what is going on and

the success of the program will create

excitement and energy

Regular communication from

leadership

Be transparent about progress and impediments

Town Halls

Executive Roundtables

Signage

Information Radiators

Cadence of Accountability

Page 108: Agile transformation Explained: Agile 2017 Session

108

STEP TEN

W H Y H O W W H A T

Understand what’s in it for everyone involved

and help them see where they fit in the

new organization

Clarity

Accountability

Measureable progress

Team assignments

Staffing plans

Job descriptions

Job aids

Communities of Practice

Page 109: Agile transformation Explained: Agile 2017 Session

M E A S U R I N G P R O G R E S S

Page 110: Agile transformation Explained: Agile 2017 Session

110110

PERFORMANCE METRICS

Page 111: Agile transformation Explained: Agile 2017 Session

111111

DELIVERY TEAMS

Sc r um

Backlog Size

Velocity

Burndown

Escaped Defects

Commit %

Acceptance % Ratio

Scope Change

PERFORMANCE METRICS

Page 112: Agile transformation Explained: Agile 2017 Session

112112

PROGRAM TEAMS

DELIVERY TEAMS

Sc r um

Kanb an

Backlog Size

Velocity

Burndown

Escaped Defects

Commit %

Acceptance % Ratio

Scope Change

Cycle Time

Features Blocked

Rework/Defects

PERFORMANCE METRICS

Page 113: Agile transformation Explained: Agile 2017 Session

113113

PROGRAM TEAMS

PORTFOLIO TEAMS

DELIVERY TEAMS

Sc r um

Kanb an

Kanb an

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

PERFORMANCE METRICS

Page 114: Agile transformation Explained: Agile 2017 Session

114114

TRANSFORMATION METRICSCapabilities Performance

Page 115: Agile transformation Explained: Agile 2017 Session

115115

TRANSFORMATION METRICSCapabilities Performance

MetricsPerformance

Page 116: Agile transformation Explained: Agile 2017 Session

116116

TRANSFORMATION METRICSCapabilities Performance

MetricsPerformance

OperationsPerformance

Page 117: Agile transformation Explained: Agile 2017 Session

A T A L E O F T W O T R A N S F O R M A T I O N S

Page 118: Agile transformation Explained: Agile 2017 Session

118118

TRANSFORMATIONS ARE UNIQUE

C O M P A N Y O N E

• 3 Teams

• No Dependencies

• Low Resistance

• Team Level

• Adaptive-Emergent

• Single Expedition

• Lean Startup

• Low Coordination

• Low Metrics and Control

C O M P A N Y T W O

• 800 Teams

• Tightly Coupled

• High Resistance

• Enterprise

• Predictive-Convergent

• Many Expeditions

• SAFe

• High Coordination

• High Metrics and Control

Page 119: Agile transformation Explained: Agile 2017 Session

119119

[email protected]

404-312-1471

www.leadingagile.com

twitter.com/mcottmeyer

facebook.com/leadingagile

linkedin.com/in/cottmeyer

MIKE COTTMEYER


Top Related