Confessions of a Coach

57
Confessions of a Coach: Agile Adoption War Stories Marko Taipale twitter: @markotaipale Potsdam, Berlin 2013
  • date post

    19-Oct-2014
  • Category

    Business

  • view

    1.884
  • download

    4

description

3 real life stories and a conclusion as presented in Agile Development Practices Potsdam/Berlin

Transcript of Confessions of a Coach

Page 1: Confessions of a Coach

Confessions of a Coach: Agile Adoption War Stories

Marko Taipale twitter: @markotaipale Potsdam, Berlin 2013

Page 2: Confessions of a Coach

Why?

Sharing is Caring!

You guys are smart - do not repeat my mistakes :)

Page 3: Confessions of a Coach

3Stories

Page 4: Confessions of a Coach

Livin’ on a Prayer

Page 5: Confessions of a Coach

Background: Subcontractor, 3 teams, customer already “agile”

Assignment: “Help us to deliver in Agile way!”

“We need expertise to deliver this on time”

Page 6: Confessions of a Coach

I had to figure out where they are

Page 7: Confessions of a Coach

600 use cases

Page 8: Confessions of a Coach

600 use cases

6 cases / month

Page 9: Confessions of a Coach

600 use cases

100 months of work

6 cases / month

Page 10: Confessions of a Coach

600 use cases

6 cases / month

100 months of work

400% improvement, 600 / 24 = 25 months

Page 11: Confessions of a Coach

600 use cases

100 months of work

400% improvement, 600 / 24 = 25 months

They got 6 months

6 cases / month

Page 12: Confessions of a Coach

What would you do?

What is the purpose of this system?

Page 13: Confessions of a Coach

Customer went crazy... and then Subcontractor

went to denial

“We just need stronger management to push this trough”

Page 14: Confessions of a Coach

I got repositioned

Page 15: Confessions of a Coach

Result: Subcontractor told that they are not going to renegotiate the deal

Lesson: Make them to study the situation and have no agenda

Page 16: Confessions of a Coach

The Goal

Page 17: Confessions of a Coach

Background: 500+ employee software company, some Scrum teams

Assignment: Improve our time-to-market

“We are way too slow!”

Page 18: Confessions of a Coach

Value Stream

Page 19: Confessions of a Coach

Order Prioritise Resource allocation

Dev & Test

Page 20: Confessions of a Coach

Order Prioritise Resource allocation

Dev & Test

8 months

2m 6m1d1d1w 1w

Page 21: Confessions of a Coach

Order Prioritise Resource allocation

Dev & Test

420 5

8 months

160

2m 6m1d1d

Active orders

Waiting for resources Released

1w 1w

Page 22: Confessions of a Coach

I took a look at how they feed the system

Page 23: Confessions of a Coach

DevDirPortfolio

Goal: profit, cost-effective, fast

Page 24: Confessions of a Coach

PO PO PO

What is the priority?

I. RegulationsII. Biz devIII. Customer reqs

DevDirPortfolio

Goal: profit, cost-effective, fast

Page 25: Confessions of a Coach

PO PO PO

What is the priority?

I. RegulationsII. Biz devIII. Customer reqs

DevDirPortfolio

Goal: profit, cost-effective, fast

Sales Dir

Bonus!

How do I get bonus?!

Goal: Growth!

Page 26: Confessions of a Coach

PO PO PO

What is the priority?

I. RegulationsII. Biz devIII. Customer reqs

DevDirPortfolio

Goal: profit, cost-effective, fast

Sales Dir

Bonus!

How do I get bonus?!

Goal: Growth!

Contract

Sanction clause

Page 27: Confessions of a Coach

PO PO PO

What is the priority?

I. RegulationsII. Biz devIII. Customer reqs

DevDirPortfolio

Goal: profit, cost-effective, fast

Sales Dir

Bonus!

How do I get bonus?!

Goal: Growth!

Contract

Sanction clause

HIGH RISK!

Page 28: Confessions of a Coach

What would you do?

What is the purpose of this system?

Page 29: Confessions of a Coach

Connect Development and Sales Directors

“We shall take care of this!”

Page 30: Confessions of a Coach

Result: a new way to control resource allocation (?!)

Lesson: Misaligned goals with incentives destroy the system performance.

There are no “evil” people rather systems that reward counter-productive behavior.

Page 31: Confessions of a Coach

The Whole

Page 32: Confessions of a Coach

Background: International gaming company, TO 100 Meur, 400+ people

Assignment: “Scale up our product development to serve the needs of the business.”

“Our product development is the bottleneck”

Page 33: Confessions of a Coach

After 2 years10+ Scrum teams,

6 week company wide sprints

We’re done, right?

Page 34: Confessions of a Coach

Business Development:

“I do not know what have you done, but we have not improved a bit...”

Page 35: Confessions of a Coach

Development

2m (6m)

Page 36: Confessions of a Coach

Development Deployment

2m (6m) 3w

Page 37: Confessions of a Coach

IdeaInternalapproval

Customerapproval Resourcing

Design Development Deployment

2h 2h

2m (6m) 3w1m

1d

Page 38: Confessions of a Coach

Idea

35

Internalapproval

Customerapproval Resourcing

Design Development Deployment

1215

2h 6m

6m 6m

1w

2h

2m (6m) 3w1m

1d1m2d

3m24m

Page 39: Confessions of a Coach

Idea

35

Internalapproval

Customerapproval Resourcing

Design Development Deployment

1215

2h 6m

6m 6m

1w

2h

Scrum!

2m (6m) 3w1m

1d1m2d

3m24m

Page 40: Confessions of a Coach

Idea

35

Internalapproval

Customerapproval Resourcing

Design Development Deployment

1215

2h 6m

6m 6m

1w

2h

Scrum!

2m (6m) 3w1m

1d1m2d

3m24m

Page 41: Confessions of a Coach

Thanks to Henrik Kniberg taking the shot! :)

Page 42: Confessions of a Coach

What would you do?

What is the purpose of this system?

Page 43: Confessions of a Coach

Development Director

“You shall not show this to anyone...”

Why?

Page 44: Confessions of a Coach

Development

3m3-6

0-3kkIdeas..

After some drastic changes...

Page 45: Confessions of a Coach

Result: Time-to-Market 24 months to 3 months

Lesson: • Beware suboptimization -> Optimize the whole• Showing it does not mean fixing it• Find a way to get commitment

Page 46: Confessions of a Coach

What can we learn from this?

Page 47: Confessions of a Coach

Thinking

System

Performance

Page 48: Confessions of a Coach

Thinking

System

Performance

Analysis Change

Page 49: Confessions of a Coach

Purpose

Metrics

Permission

Change

Context

Page 50: Confessions of a Coach

Purpose

Metrics

Permission

Change

Clarify the purpose of the company (from customer point of view)

Measure how the system fulfills it’s purpose

Context

Get the permission (and commitment) for change

Understand the boundaries and SWOT

Change the system, only implement changes that are relevant to the purpose

Page 51: Confessions of a Coach

Purpose

Metrics

Permission

Change

Context

Coach the management to do this

Page 52: Confessions of a Coach

Purpose

Metrics

Permission

Change

Context

PDCA cycles

Page 53: Confessions of a Coach

It is not about agile or lean...... nor transformation

Page 54: Confessions of a Coach

It is not about agile or lean...... nor transformation

It is about the system...

... and fulfilling the purpose of the system

Page 55: Confessions of a Coach

It is not about agile or lean...... nor transformation

You are not going to change a thing...... but you can initiate the change

It is about the system...

... and fulfilling the purpose of the system

Page 56: Confessions of a Coach

Marko Taipale• Principal consultant with agile/lean mindset, CTO, Advisor

• 15+ years of software development

• Capabilities to deliver products from concept to cash

• Tens of public speaking appearances

International online gaming company (TO 100+ Meur) improved time-to-market from 24 months to 3 months

Energy company purchased process control system and got the delivery 4 times faster than expected. The system secured the business for next 2 years.

Software company validated new business model for new product in 2 months.

Software product company saved 1,3 Meur / year in management and administration.

Page 57: Confessions of a Coach

Please  evaluate  my  presenta/on  by  using  the  evalua/on  booklets  which  you  can  find  in  your  conference  bag.Thank  you!