lessons learned scaling kanban in a large organization

Post on 10-Dec-2014

320 Views

Category:

Business

1 Downloads

Preview:

Click to see full reader

DESCRIPTION

It’s common to see an organization (the people in them) focus on building products with as many features as possible and targeting delivery by a specific due date. Yet, often the result is missing the date while ignoring important goals demanded by the businesses such as high levels of product quality, development productivity, planning reliability, employee satisfaction, and customer loyalty. Retrospectives, if done after such an occurrence, surface the dissatisfaction concerning missed dates, poor quality, technical debt, and more, still frequently this pattern repeats.

TRANSCRIPT

Richard HensleyAVP ProcessMcKesson Corprichard.hensley@mckesson.comrhensley99@msn.comwww.linkedin.com/in/richardhensley

Lessons Learned Scaling Kanban in a Large Organization

• Stable, Deep Rooted Traditions• 175 year old drug distribution company• More than 100 billion dollars in revenue• More than 35 thousand employees• Worldwide operations

Copyright 2012 - Richard Hensley

Working with the people in your

system so that way your business

team thinks and the way your

product development team executes

are in alignment

Goal of This Talk

Business and technology can peacefully co-create!

Alignment

Copyright 2012 - Richard Hensley

• Growth Business• Federation of 3 Businesses• Change Target

– Product Development– Product Management– Documentation Development– Training Development– Clinical Content

Development– Product Strategy– Product Services

McKesson Health Solutions

Copyright 2012 - Richard Hensley

When is it going to be done? What is it going to cost?

What Matters

Copyright 2012 - Richard Hensley

Kanban MethodPeopleBusiness System

Topics

Copyright 2012 - Richard Hensley

4 Principles

1. Start with what you do now

2. Agree to pursue incremental, evolutionary change

3. Initially, respect current roles, responsibilities, and job titles

4. Encourage acts of leadership at all levels in the organization

6 Core Practices

1. Visualize

2. Limit Work-In-Process (WIP)

3. Manage Flow

4. Make Management Policies Explicit

5. Develop feedback mechanisms at workflow, inter-workflow, and organizational levels

6. Improve collaboratively using “Safe to Fail” experiments

Kanban Method in One Page

Copyright 2012 - Richard Hensley

People

Copyright 2012 - Richard Hensley

Disinterest to Engagement to Ownership

Copyright 2012 - Richard Hensley

Change Journey

Copyright 2012 - Richard Hensley

People are Social

Copyright 2012 - Richard Hensley

Mystery and Imagination

Copyright 2012 - Richard Hensley

Frequently Expose a Bit

Copyright 2012 - Richard Hensley

Going Viral

Copyright 2012 - Richard Hensley

Continuously Improve

Copyright 2012 - Richard Hensley

Watch Out

• Resistors• Dangerous Enthusiasm• Improvements with Wild Abandon• Shotgun Metrics• Stigmatizing Change with Negative Events

Copyright 2012 - Richard Hensley

Let’s Chat

Copyright 2012 - Richard Hensley

Business System

Copyright 2012 - Richard Hensley

Starting Up – Creating a Sturdy Foundation

• Start with what you do now• Apply the core practices of Kanban• Start within a safe scope of authority and influence• Add to your system within your scope of comfortable influence• Add to your system as the viral nature takes a-hold

Copyright 2012 - Richard Hensley

Construct Quality

Copyright 2012 - Richard Hensley

Construct Quality Deliver Deploy

Copyright 2012 - Richard Hensley

Analyze DesignConstru

ctQuality Deliver Deploy

Copyright 2012 - Richard Hensley

Copyright 2012 - Richard Hensley

Scaling Up – Engaging the Business

• Dates and Dollars• Model Future Performance• Whole System Accountability

Copyright 2012 - Richard Hensley

Dates and Dollars

Copyright 2012 - Richard Hensley

Model Future Performance

Copyright 2012 - Richard Hensley

Whole System Accountability

Copyright 2012 - Richard Hensley

Scaling Out – Engaging Across the Portfolio

• Cross Appropriation• Catalog the ideas from each implementation• Use the ideas in each new implementation• Do not assert the ideas into the implementation

• Reconfiguration• Change ideas from you catalog to be appropriate in your new

implementation• Articulation

• Document and report out how the ideas have changed• With each new business you are starting over without starting from

the beginning

From Disclosing New Worlds by Charles Spinosa, Fernando Flores, Hubert L. Dreyfus

Copyright 2012 - Richard Hensley

Working with the people in your

system so that way your business

team thinks and the way your

technology team executes are in

total alignment

Checking in on the Goal

Business and technology can peacefully co-create!

Alignment

Copyright 2012 - Richard Hensley

Let’s Chat

top related