Taking Flight AgileDC 2014

105
Taking Flight From Aspiration to Transformational Action

Transcript of Taking Flight AgileDC 2014

Page 1: Taking Flight AgileDC 2014

Taking Flight

From Aspiration to

Transformational Action

Page 2: Taking Flight AgileDC 2014

Your Aviator…

Software Leadership Coach w/24 years IT Experience/23 years S/W Development

21 years Management Experience

Deming, Reengineering, Agile/Lean

Military/Federal(Inside & Outside)

Product Companies

Multiple Industries

16 years Acquisition Experience

Active Agile Community Member(Agile Coach Camp/Agile Influencers of DC)

(GLASScon/LeanCoffeeDC)

Lean Start-up & Product Mgmt

Page 3: Taking Flight AgileDC 2014

WHYWHATHOW

Want better results for our business (& us)

Change to get these results

Operationalize & sustain change

Agile Transformation (Transition, Adoption, etc.)

Page 4: Taking Flight AgileDC 2014

Agile Transformation is

strategic innature.

(Transition, Adoption, etc.)

Page 5: Taking Flight AgileDC 2014
Page 6: Taking Flight AgileDC 2014

Top 2 Reasons Agile Projects Failed

Company philosophy/culture at odds w/core agile values

External pressure to follow traditional waterfall processes

Ability to Change Org Culture 53%General Resistance to Change 42%Trying to fit Agile into into non-Agile framework 35%Personnel w/Agile Experience 33%Management Support 30%

Top 5 Barriers to Agile Adoption

Sources: VersionOne State of Agile Survey 2013

Culture

Page 7: Taking Flight AgileDC 2014

2012Ability to Change Org Culture 52%General Resistance to Change 41%Trying to fit Agile into into non-Agile framework 35%Personnel w/Agile Experience 33%Management Support 31%

Top 5 Barriers to Agile Adoption

2011Ability to Change Org Culture 52%Personnel w/Agile Experience 40%General Resistance to Change 39%Management Support 34%Project Complexity 30%

2010Ability to Change Org Culture 51%General Resistance to Change 40%Personnel w/Agile Experience 40%Management Support 34%Project Complexity 31%

Sources: VersionOne State of Agile Surveys 2010-12

Culture

Culture

Top 2 Reasons Agile Projects Failed

Company philosophy/culture at odds w/core agile values

External pressure to follow traditional waterfall processes

Page 8: Taking Flight AgileDC 2014

“Culture eats Strategy for breakfast.”- Peter Drucker

Page 9: Taking Flight AgileDC 2014

Culture

Behaviors That Are Not Tolerated

Tolerated Behaviors

Preferred Behaviors

Page 10: Taking Flight AgileDC 2014

We’ll start

3 modelswith

Page 11: Taking Flight AgileDC 2014

Accredited to Michael Sahota & Olaf Lewitz

Page 12: Taking Flight AgileDC 2014

Collaborative Control

CompetencyCultivation

Schneider Cultural Model

Rea

lity

Ori

ente

dPo

ssib

ility

Ori

ente

d

People Oriented Org Oriented

The Reengineering Alternative, William Schneider

Page 13: Taking Flight AgileDC 2014

Using the Schneider Model

• Plot organizational characteristics onto its grid– Subjective in nature (acknowledgement)

• Where the largest cluster occurs, this is your dominant culture

• You may have “sub-cultures” that are different• A culture may straddle borders• A new organization may not yet have a dominant

culture• Recommend also plotting where you want your

dominant culture to be…

Page 14: Taking Flight AgileDC 2014

Adapted from Dr. Ahmed Sidky’sUnlocking the Blackbox of Agile

Page 15: Taking Flight AgileDC 2014

Culture Habits Decisions

Evolutionary Theory of Economic Change,Richard Nelson & Sidney Winder, 1982

Page 16: Taking Flight AgileDC 2014

Many ‘solution’ decisionsare captured in

the organizational

and its

paths

structure

communication

Conway’s Law is alive and well.

Page 17: Taking Flight AgileDC 2014

Business Value Stream(s)

Page 18: Taking Flight AgileDC 2014

Business Value Stream(s)

Page 19: Taking Flight AgileDC 2014

Business Value Stream(s)

SDLC Value StreamSDLC Value StreamSDLC Value Stream

Page 20: Taking Flight AgileDC 2014

Customers

Line(Mission)

Support

Strategy

Value Streamsbecome

entangledin the

hierarchy

OpsMgmt

Page 21: Taking Flight AgileDC 2014

Customers

Line(Mission)

Support

Strategy

Value Streamsbecome

entangledin the

hierarchy

OpsMgmt

-- truly --

(Only one truly tangled value stream shown…)

Page 22: Taking Flight AgileDC 2014

Most organizations don’t make fully rationale decisionsthose decisions are unknowingly steeped in their habits.

Evil is committed by

the well-meaning

The Power of Habit, Charles Duhigg

Page 23: Taking Flight AgileDC 2014

Stacey Decision-Making Model

(Perception of) Understanding of Problem

Ag

reem

ent

on

Res

olu

tio

n

Page 24: Taking Flight AgileDC 2014

Decisions Δ Habits Δ Culture

Page 25: Taking Flight AgileDC 2014

Taking Flight Approach

• Set an aspirational target

• Examine possible routes

• Select the best route and the first waypoint(s)

– Consider each leg an experiment

– Work details/make decisions operationally

– Inspect & Adapt at each waypoint

– Make course corrections

– Squadron mates

Page 26: Taking Flight AgileDC 2014

Establish an Aspirational Vision of your future

Page 27: Taking Flight AgileDC 2014

Aspiration :: (noun)

1. strong desire, longing, or aim; ambition

2. a goal or objective desired

Page 28: Taking Flight AgileDC 2014

End State :: (noun)

1. The set of required conditions that defines

achievement of the commander's objectives.

Page 29: Taking Flight AgileDC 2014

Aspirational vs End State

• Any end state you choose may be wrong (don’t use BUFD for your Org Change)

• No defined end state = never done assists mindset Δ– Revisit aspiration and progress towards it regularly

– Use interim states that move you in the right direction and are more concrete

– Continual experiments/Contained failures

– It’s how you apply Product Thinking to your organization

• Aspirations can more easily balance between the soft and hard skills needed

Page 30: Taking Flight AgileDC 2014

In terms of

A vision

AspirationsOrganizational Transformation,

are…

not too complex

The set of characteristics based on this vision

Page 31: Taking Flight AgileDC 2014

Why is Setting an Aspiration Important?

• Cast what the transformation means to the organization; personalize it – includes a ‘business’ (or mission) view

• Determine what the most relevant principles from Agile (or Lean, or Craftsmanship) mean to the organization

• Guides decisions within the organizations; achieves alignment (including the business)

• Provides guidance for course corrections once we go in-flight

Avoids Imposed Agile…

Page 32: Taking Flight AgileDC 2014

Who are thecustomers

of your organization’s

change effort?

Page 33: Taking Flight AgileDC 2014

The

in the people

organization

Page 34: Taking Flight AgileDC 2014
Page 35: Taking Flight AgileDC 2014

4 Types of Co-Creation (mapped to Culture types of Schneider Model)

Collaborative Cultivating

Competency Controlling

Page 36: Taking Flight AgileDC 2014

Howdo I

determine

which one?

Page 37: Taking Flight AgileDC 2014

By Asking…

Controlling Invitation/Mandate to ‘Influencers’

Competency Invitation/Inclusion of Relevant/Knowledgeable

Collaborative Invitation for Those Interested

Cultivating Invitation/Reachout to Network of Interest

Page 38: Taking Flight AgileDC 2014

4 Types of Co-Creation (mapped to Initial Engagement Activities )

Open Space Open Space|World Café

Workshops|World Café Workshops

Page 39: Taking Flight AgileDC 2014

Lots of Approaches to Creating One

Lego for Serious Play

KrisMap

Vision Statements

Cover Story Innovation Game

We want common agreement & understanding…

Participatory Creation > Clear Communication > Proclamation

Page 40: Taking Flight AgileDC 2014

“Deliver business value daily.”“Constantly improve delivery,reducing waste and through new ideas.”

Page 41: Taking Flight AgileDC 2014

Collaborative Control

CompetencyCultivation

Aspiration on Schneider Cultural Model

Rea

lity

Ori

ente

dPo

ssib

ility

Ori

ente

d

People Oriented Org Oriented

Collaborative

Innovative

Resourceful/Can-DoOptimistic

Pragmatic

Adds Value

Cost ConsciousConsiderate

Organized

Risk Taker

Responsive

Decisive

FlexiblePositive Attitude

Sense of Humor Speedy

Stamina

Motivated

Integrity

Reader

Focused on Business Results

Confident

Empathetic

Reliable

One Voice

Page 42: Taking Flight AgileDC 2014

we have a

how do weTarget Aspiration,

Now that

incremental step?determine

the next

Page 43: Taking Flight AgileDC 2014

the Current State

Understand

Page 44: Taking Flight AgileDC 2014

Lots of Approaches to This Too…

Process Models

SWOT Analysis

Customer Personas

Business Model Canvas

Select the appropriate mix…

Participatory Creation > Clear Communication > Proclamation

Page 45: Taking Flight AgileDC 2014

AspirationStarting

Point

Page 46: Taking Flight AgileDC 2014

and

Operational ActionsPrioritize

Determine

toachieve

the Next Statecongruent

Visionwith the

Page 47: Taking Flight AgileDC 2014

Takesimple

stepsP

PSimple does not imply easy…

Page 48: Taking Flight AgileDC 2014

Lots of Approaches to This Too…

Forcefield Analysis

Strategy Maps

Priority vs Energy Exercises

Business Model Canvas

Select the appropriate mix…

Participatory Creation > Clear Communication > Proclamation

Page 49: Taking Flight AgileDC 2014

Goal: Roadmap of Prioritized Δsfor

Incremental, Relative Improvement

Page 50: Taking Flight AgileDC 2014

Current State

Aspiration

Next State

Process Δs

OrgStructure

Δs

NewPractices

Habit Δs

Adapted from Organizational Transitions,by R. Beckhard & R.T. Harris

Page 51: Taking Flight AgileDC 2014

Many Things to Change Depending on What’s Next in Priority

• New Strategies

• New Org Structures

• Find/Establish New Support Networks

• New Practices

• New/Streamlined Processes

• Rewards for Δ in Behaviors

• Create/Eliminate Ceremonies

• New Habits The Hardest to Do

& the most crucial

Some ofthese will be Experiments

Page 52: Taking Flight AgileDC 2014

Decisions Δ Habits Δ Culture

Page 53: Taking Flight AgileDC 2014

Find Key Practices to avoid being eaten…Habits

Page 54: Taking Flight AgileDC 2014

What Might Be Some of the Habits We Want to Change?

• Ways meetings are conducted

• Ways meetings are scheduled

• How managers give feedback

• What agreements are explicit or implicit

• How decisions are made and owned

• Whether people show vulnerability

• How people learn new skills Use as an example

Note: want org habits reinforcing an Agile mindset

Page 55: Taking Flight AgileDC 2014

Habit Loop

Habit

Trigger RewardCraving

The Power of Habit – Charles Duhigg

OldNew

Page 56: Taking Flight AgileDC 2014

Training

Need to Know

Something NewRecognition

Craving

For

Recognition

Example Org Habit Around Training

Page 57: Taking Flight AgileDC 2014

Training

Need to Know

Something NewRecognition

Craving

For

Recognition

Example Org Habit Around Training

self-study/experimentation=Learning

Page 58: Taking Flight AgileDC 2014

Finding Leverage Points

• The habit to change is formal training to learning

• Step 1: Habit Loop Causality Diagram

• Habit Loop will reveal underlying complexity

– More Steps

– Reinforcing Loop

• Step 2: Look for Limiting Conditions & Side Effect Loops

self-study/experimentation=

Page 59: Taking Flight AgileDC 2014

Training

Request

Need to Know

Something New

Recognition

Formal

Training

Full Causal Diagram

Fulfill IDP or

Certification

Easy to

Measure

Statement

of Intent

Self-Study

Experiment

Absorb

& Share

Learning

Learn the

Lingo to

“Look Smart”

Get By/

Impress

Lack of

Failure

Shows

Vulnerability

Avoids Showing

Vulnerability

Page 60: Taking Flight AgileDC 2014

Current State

Aspiration

Next State

Process Δs

OrgStructure

Δs

NewPractices

Habit Δs

Manage the Δ

Adapted from Organizational Transitions,by R. Beckhard & R.T. Harris

Page 61: Taking Flight AgileDC 2014

“No plan survives contact with the enemy.”

- Helmuth von Moltke the Elder

Page 62: Taking Flight AgileDC 2014
Page 63: Taking Flight AgileDC 2014

Inspect + Adapt

Page 64: Taking Flight AgileDC 2014

Value Stream(s)

Org

Retro

What So What

Now

What

Measures

Retrospectives for Organizational Change,Jutta Eckstein

Page 65: Taking Flight AgileDC 2014

Org

Retro

What So What

Now

What

Gather Data

Generate Insights

DecideData

(Measures/

Perspectives) Execute Δs

Open

Close

Value Stream(s)

Page 66: Taking Flight AgileDC 2014

Status Quo

New Status Quo

disruption amount

disruption time

Satir Change Curve

A detailed depiction of the Satir Change model -http://stevenmsmith.com/ar-satir-change-model/

Page 67: Taking Flight AgileDC 2014

How can we promote Sustainable Change?

Page 68: Taking Flight AgileDC 2014

Definitions

Sustainable :: Able to be maintained at a certain rate or level. Synonym: Supportable

Change :: The act or instance of making or becoming different. Synonyms: Alteration, Shift, Mutation

“Change Capacity”

Page 69: Taking Flight AgileDC 2014

To-Do In Work Done

Organizational Change CapacityWIP Limit =

Page 70: Taking Flight AgileDC 2014

+

=limit to change

> disruption amount Capacity is the WIP

Page 71: Taking Flight AgileDC 2014

+

net effect time

tolerance to time-lagdefined by environment

=

Page 72: Taking Flight AgileDC 2014

+net effect

time balance limit vs lag

Page 73: Taking Flight AgileDC 2014

AspirationStarting

Point

Promotes

Restricts

Promotion/Restriction based on Limits to Organizational Change

by Herbert Kaufman& Discussions @ #CultureDC

Cross-cutting Teams

Diversity (of thoughts)

Failure Tolerance

Clear Vision

Employee Orientation

Experimentation

Transparency

Hiring to Complement

Page 74: Taking Flight AgileDC 2014

AspirationStarting

Point

Promotes

Restricts

Low Risk Tolerance

Grand Unclear Vision

Hiring to Fit

Insular Communication

Employee Indoctrination

Successes Only

Promotion/Restriction based on Limits to Organizational Change

by Herbert Kaufman& Discussions @ #CultureDC

Cross-cutting Teams

Diversity (of thoughts)

Failure Tolerance

Clear Vision

Employee Orientation

Experimentation

Transparency

Hiring to Complement

Specialized Silos

Group Think

Page 75: Taking Flight AgileDC 2014

Current State

Aspiration

Next State

Process Δs

OrgStructure

Δs

NewPractices

Habit Δs

Manage the ΔΔ Kanban

Δ Validation Board

Adapted from Organizational Transitions,by R. Beckhard & R.T. Harris

Page 76: Taking Flight AgileDC 2014

Determinethe

Change Domain

Make change,Monitor for results

Retrospect,Decompose

Experimentfor Solutions

Solve, Observe patterns

Cynefin Framework, David Snowden

Page 77: Taking Flight AgileDC 2014

Next Up In-WorkBacklog Complete

Transformation KanbanReady Measure Done

Page 78: Taking Flight AgileDC 2014

Next Up In-WorkBacklog Complete

Transformation KanbanReady Measure Done

BasedOn Org

Capacity

BasedOn Org

Capacity

BasedOn

Org &Capacity

To Measure

BasedOn

Org &Capacity

To Measure

BasedOn Org

Capacity

Organizational WIP

Team has• Capacity• Charter• Measures• Expected

Outcomes

Team has• Completed

Actions

Team has• Measured

Results

Page 79: Taking Flight AgileDC 2014

How do we figure out how much change to pull?

1. Hypothesis use communications paths as a starting point; • capacity = comm paths

N ppl involved• hierarchy comm paths = direct report lines• team comm paths = ∑(1+…+N-1)• can have hybrids

2. Modified by Team Size

3. Multiplied by reinforcing loops

4. Consider like mid-size “story” (in terms of points); every org will be different & large single changes can out-strip capacity and need to be broken down

Page 80: Taking Flight AgileDC 2014

Team Size

5 9 157

“Is Five the Optimal Team Size?”, infoQ, Vikras Hazrati & Jurgen Appelo on http://noop.nl

Scrum teams 7 +/-2

S = ƒ({P},E)where, P = personalities

E = environment

5 Best for deep comm, 15 most for deep trust, 150 most for comm

≥ 1≤1 <1

Page 81: Taking Flight AgileDC 2014

Change Multiplier

Hire for diversity

Display transparency in decisions

Allow experimentation

Establish clear vision ≥1

Punish failure

Decisions made w/littleno input

Hire yes people <1

Safety

Only concern: people’s performance

on the job

Page 82: Taking Flight AgileDC 2014
Page 83: Taking Flight AgileDC 2014

Validation Board

Assumptions

Benefactor

Issue

Solution

P1 P2 P3 P4 P5

Riskiest Assumption

Experiment

Result

Invalidated Validated

Hypothesis

Page 84: Taking Flight AgileDC 2014

Squadron Mates

• Create a support network

• Find like minds and pair

– Sounding board for pragmatic decisions

• Better yet, form a triad

– Third person holds the commitments of the other two to each other accountable

• Grow network as pairs/triads

– Net-Map Technique is a great tool here

Triads come from The Culture Game by Daniel MezickNet-Map Toolkit, Eva Schiffer, http://netmap.wordpress.com

Page 85: Taking Flight AgileDC 2014

Leadership

• Servants to their teams

• Provide the right environment– Transparent

– Cooperative

– Enabled

– Empowered

• Tell stories: – Where we have been

– Where we are going

– Both successes and failures

Page 86: Taking Flight AgileDC 2014

of

andHidden Assumptions

Biases

Page 87: Taking Flight AgileDC 2014

A Couple of Typical Biases or Assumptions

• People just don’t want to change– So explain to me why people will take up a new hobby

later in life or move across country? (Hint1: it is in their interest – find mutual desire)(Hint2: involve them)

• Agile has issues scaling to large programs– Why do you have a program? Could this be solved in a

different manner with sets of smaller applications?(Hint1: most “programs” are put together for reasons other than actual size & complexity, such as ability to get budget, the size/complexity is an outcome from these reasons/decisions)(Hint2: descale to individual applications before adopting a scaling framework – scale agility not the organization)

Page 88: Taking Flight AgileDC 2014

Adding Bureaucracy

Will Not Create Success

Page 89: Taking Flight AgileDC 2014

Most Programs

Adapted by Jurgen Appelo from the Cynefin framework; posted on his blog at http://noop.nl

Tend to be here!

Page 90: Taking Flight AgileDC 2014

Most PoliciesTend to be here!

Page 91: Taking Flight AgileDC 2014

Agile TeamsTend to be here!

Page 92: Taking Flight AgileDC 2014

Complicated + ComplexOverrides Ordered + Simple

+ =Process Team Result

Page 93: Taking Flight AgileDC 2014

1

2

3

n Worse Case

Best Case

Page 94: Taking Flight AgileDC 2014

Strive to decomplicate…Help teams operate as simple and ordered as possible.

Page 95: Taking Flight AgileDC 2014

Apply the pants principle…Simple process adopted by the team doing the work in a simple structure.

+Process Team

Page 96: Taking Flight AgileDC 2014

Customers

Strategy

Value Streamsyour

Detangle

OpsMgmt

Line(Mission)

Support

Line(Mission)

Team

Page 97: Taking Flight AgileDC 2014

Customers

Strategy

Value Streamsyour

Detangle

OpsMgmt

Line(Mission)

Support

Line(Mission)

Teams

Page 98: Taking Flight AgileDC 2014

Customers

Strategy

Value Streamsyour

Detangle

OpsMgmt

Line(Mission)

Support

Page 99: Taking Flight AgileDC 2014

Customers

Line(Mission)

Teams

SupportServices

Strategy

Value Streamsofa Network

PortfolioSupport

to

Page 100: Taking Flight AgileDC 2014

CustomersLine

(Mission)

Support

Strategy

Value Streamsofa Network

PortfolioSupport

to MeritocraticAutonomousTeamEnvironment

Page 101: Taking Flight AgileDC 2014

What is MATE?

Meritocratic

Autonomous

Team

Environment

Assessed by peers based on Biz Value Stream

Teams make their own Decisions

Primary structure is the team

Teams have the support needed to be successful

Page 102: Taking Flight AgileDC 2014

Drawing: Alex Hughes

Δ

Page 103: Taking Flight AgileDC 2014

Thanks!and

Have aGood Flight!

Page 104: Taking Flight AgileDC 2014

Government Lean-Agile Software & Systems Conference

GLASScon

Stay tuned at http://glasscon.usAnd on Twitter: http://twitter.com/GLASScon4gov

Coming Nov 2014

Page 105: Taking Flight AgileDC 2014

Paul M. [email protected]

[email protected]@paul_boos

703-307-4322 (mobile)

Look for a ‘workbook’ on this in the near future…