IAD2015 lean&agile trasformation-story

29
Lean & Agile Transformation Story Daniela Cecchinelli – IAD 2015 Brescia

Transcript of IAD2015 lean&agile trasformation-story

Lean & Agile Transformation Story

Daniela Cecchinelli – IAD 2015 Brescia

Agile Master

4

Transformers: CHANGE 2 WIN

Unlike old reorganization changes

the Transformers' Initiative shall drive

change from within, facilitating the

Lean Agile adoption & transition, and

supporting Scrum and Kanban teams,

as well as Communities of Practice,

in improving Neomobile business,

speediness and innovation.

We aim to Change 2gether

in order 2win the fast and

exciting innovation challenges

""

To reach our Vision, we should eliminate

the barriers and the resistance into the

company, creating opportunities by using

a Lean Change approach.

We will communicate the right

messages, give to people the answers

they expect, and create a climate of

trust, commitment and transparency

as claimed by Lean Agile Values.

CHANGE 2 WIN: Mission

Our Decepticons

Lone Nut + Coach + CTO = > Assessment + Workshop

Lone Nut

start

Kotter’s steps to Change

A

D

A

P

T

Awareness that the current approach isn’t working

Desire to change

Ability to work in a lean and agile manner

Promote early successes to build momentum and get others to follow

Transfer the impact of agile throughout the organization so that it sticks

ADAPTing to Agile Development

CEOCTO

CFO

PEOPLE Director

Program Management Exe. Director

International Operation

Exe. Director

Transformers: who we are

Transformers: who we are

Lean Change Management

How we work

“We hypothesize by<implementing this Option>

we will<solve this problem / Insights>

which contributes to<this experiment on our canvas>

as measured by<this measurement> ”

How we work

Our Boards: Change Canvas

Our Boards: Experiment board

February March April May June July

TRAINING INCEPTION SCRUM

TRAINING INCEPTION LCM

TRAINING INCEPTION Kanban

TRAINING INCEPTION Kanban

INCEPTION SCRUM Light

Global Retrospective

Scrum

Country 1

Country 2

CoPs

What we have done: pilots

Global Retrospective

Pilot

August September October November December

SCRUM

Transformers

TRAINING INCEPTION

TRAINING

KanbanSupport

INCEPTION KanbanData & BI

AJC – Architecture - SCRUM Light

CoPs

IC_ORG

MVP Realized

INCEPTION

Country 1 - Kanban

Country 2 - KanbanNew

Inception

TRAINING INCEPTION KanbanCountry 3

CoPs

Country 4

New REUS Teams

TRAINING INCEPTION Kanban

TRAINING INCEPTION Kanban

What we are doing: second step

Scaling Lean&Agile: Program, Portfolio Level

Advanced Training Upper Stream Value, Prioritization Criteria

Lean Startup

Coaching 2 in HQ, 1 in Reus Office

MVOrg

What we are doing: second step

10 Offices Worldwide260 People

70 Kanban or Scrum26 ready for Training

53% Tech 47% Business

64% in Rome HQ

1 Scrum10 Kanban

HQ Worldwide

Some numbers

10%36%

TEAM• we didn’t understand how to interact properly with the

coach (perhaps we were scared about the Change???)• Few team members were not Early Adopter so, after a very

critical situation the LCC was disbanded by the Coach and started working on the right path.

• 11-1-2 = 8 +1 (CFO)

Learning (Shu – Ha – Ri)• Team didn’t catch the importance of study and learning• We encountered issues in understanding how to work

following the Lean Change approach

Communication• After few months we realized that few people in the

company really knew and understood our work and the meaning of Change, so we organized others communication experiments: the physical board and the “I want you” calling.

What we have learned

• SCRUM team released MVP with high «quality» (product & code)

• Jargon • Visualization & Use of Information Radiator• Transparency & Trust• All company initiatives are almost consistent with the change• People and interaction over process and tools (TFS)

• New Vision + Mission + Company Values + Working Agreements

Success & Failure

• No good in marketing for Change Management• No so good in using Lean Change Management (setting

of the wall and Board in Jira)• Juniority at all level• Lack of Scrum Master• CoP Architecture• Mindset (Fear and Resistance about Change)

Success & Failure

Thank you!

Questions?