beginning the kanban journey at an enterprise it - case study - pelephone

17
Pelephone IT – Case Study Agile Israel 2012

Upload: agilesparks

Post on 06-Sep-2014

1.088 views

Category:

Technology


3 download

DESCRIPTION

Beginning the Kanban journey at an Enterprise IT - Case study - Pelephone By Hanan Alexander @ AgileIL12 http://agilesparks.com/KanbanPelephone-HananAlexander

TRANSCRIPT

Page 1: Beginning the Kanban journey at an Enterprise IT - Case study - Pelephone

Pelephone IT – Case StudyAgile Israel 2012

Page 2: Beginning the Kanban journey at an Enterprise IT - Case study - Pelephone

Agenda Why am I here?

What made us go Agile?

Why was it so difficult?

What have we done????

What’s next?

What do we recommend you to do/not to do?

Page 3: Beginning the Kanban journey at an Enterprise IT - Case study - Pelephone

3

Why am I here?

Hopefully help other Enterprise IT organizations

advance to agile methodologies

Learn from our mistakes

Hear what worked for us

Convince the skeptic that Agile/Kanban is possible

and even recommended for Enterprise IT

organizations

Page 4: Beginning the Kanban journey at an Enterprise IT - Case study - Pelephone

4

What made us go Agile?

“After so many good years… why change?”

Time to market - 10 months!!!

Things become irrelevant (usually when we finish

coding…)

Regulation

Business people always complaining no matter what

we do…

2345678910

1 0

DesignDevelopQA

Page 5: Beginning the Kanban journey at an Enterprise IT - Case study - Pelephone

5

What made us go Agile?

Changes = Big frustration (also for us )

Everybody blaming everybody for bad quality and for

not delivering working software on time

We are not sure what , but something is not

working!

Page 6: Beginning the Kanban journey at an Enterprise IT - Case study - Pelephone

6

Why was it so difficult?

Change is never easy

Legacy systems

Legacy people

Internal political issues

Page 7: Beginning the Kanban journey at an Enterprise IT - Case study - Pelephone

7

Why was it so difficult?

Lack of knowledge and experience

We have a monopoly over IT in Pelephone (no

competitors)

Maintenance of production by the dev teams

Page 8: Beginning the Kanban journey at an Enterprise IT - Case study - Pelephone

8

What have we done???? First – Learn and Exercise

Kanban workshop for managers

Introduction to Agile

2 days workshop for dev leaders with Agile Sparks

(Yuval Y.)

Second - Decide

Page 9: Beginning the Kanban journey at an Enterprise IT - Case study - Pelephone

9

What have we done??Jump into the cold water… together…

Page 10: Beginning the Kanban journey at an Enterprise IT - Case study - Pelephone

10

What have we done

Dev helps QA to clear backlog

Production every 1 month

Assemble heterogeneous teams

Learn as we go…

Page 11: Beginning the Kanban journey at an Enterprise IT - Case study - Pelephone

11

What have we done

Some basic principles :

Sticky notes

Ceremonies

Team daily meetings

Managing WIP limit

Decomposition to stories

Page 12: Beginning the Kanban journey at an Enterprise IT - Case study - Pelephone

12

What have we doneImmediate challenges

Too big/long :

Daily meetings

Teams

Stories

Not enough retrospectives

QA are not pleased with getting software

almost all the time instead of one shot as before

Hierarchical TL’s job description becomes vague

Page 13: Beginning the Kanban journey at an Enterprise IT - Case study - Pelephone

13

What have we doneImmediate improvements

Teams are eager to succeed

People work together (No one to blame)

Everybody is involved right from the

beginning

Mean TTM shortened to 4 weeks!!

Page 14: Beginning the Kanban journey at an Enterprise IT - Case study - Pelephone

14

What have we doneImmediate improvements

Business gets working software in small chunks and

likes it

Business start to think more Agile

We are TOO FAST!!??

“Can you hold this for a week? We didn’t finish training”

“You are saying YES more then before”

“We feel that we are together in this”

Page 15: Beginning the Kanban journey at an Enterprise IT - Case study - Pelephone

15

What’s next?

Continue improving our skills

Build better (shorter, independent) stories

Conduct more efficient ceremonies

Make team members take more responsibility over project

goals

Focus on measurement

Page 16: Beginning the Kanban journey at an Enterprise IT - Case study - Pelephone

16

Recommendations

This is not a “one shot” change. Making mistakes is

part of the learning. Make sure you learn from them

Business have to prepare for minor (hopefully)

delays in first period and agree to this

People will complain at first. Embrace them but don’t

let them feel that you are afraid as much as they are

. Things will improve!

Managers should be part of the process

Page 17: Beginning the Kanban journey at an Enterprise IT - Case study - Pelephone

Questions?