Myths & benefits of kanban @ATMs 2nd Meetup_aug05

Aug 05, 2017

around 9

Pursuing

certified

SM - 50%AC - 19%PO - 6%Dev - 6%SM (2-3) - 19%

We use Kanban board just as a Visual Board to Track our work

Myth 1:

Kanban is too complex to adopt

Myth 2:

Start with Scrum, Move to Kanban

Myth 3:

Kanban is Scrum, without Iterations

Myth 4:

We cannot estimate our work in Kanban

Myth 5:

We cannot have Review and Retrospective in Kanban

Myth 6:

Kanban is only for Support Engagements, no Dev project can be

implemented

Myth 7:

Either use Kanban or Scrum

Myth 8:

We cannot perform Predictability

Myth 9:

Lets have only Basic Board

Myth 10:

We dont have ceremonies in Kanban

Myth 11:

We must focus on this as Evolutionary Approach

Lets talk on

Developed by Taichi Ohno, an industrial engineer at Japan in 1940s

Designed after shelf-shocking techniques used by supermarkets

Demand controlled system where Replenishment happened based on market/business condition

Based on a pull based system

Use of visual sign was essential to system

Kanban written in Kanji (chinese character)- that means sign or large visual board

Kanban written in Japanese alphabet Hirangana that means, Signal Cards

@

Foundation Practices

k

Systems Thinking Approach to Introduce Kanban


Understand what makes the service fit for purpose Understand sources of Dissatisfaction regarding current delivery Analyze sources of and nature of demand Analyze current Delivery Capability Model the Service Delivery Workflow Identify and Define Classes of Services Design the Kanban System Socialize Design and Negotiate Implementation

Understand what makes the service fit for purpose Understand sources of Dissatisfaction regarding current delivery Analyze sources of and nature of demand Analyze current Delivery Capability Model the Service Delivery Workflow Identify and Define Classes of Services Design the Kanban System Socialize Design and Negotiate Implementation

Evolve and Iterate


Understand what makes the service fit for purpose Understand sources of Dissatisfaction regarding current delivery

Analyze sources Of and nature of demand Analyze current Delivery Capability Model the Service Delivery Workflow Identify and Define Classes of Services

Design the Kanban System Socialize Design and Negotiate Implementation


(Reverse)

Understand Sources of Dissatisfaction regarding current delivery

Analyze sources of and nature of demand

Analyze current Delivery Capability

Model the Service Delivery Workflow

Identify and Define Classes of Services

Design the Kanban System



(Reverse)

Understand Sources of Dissatisfaction regarding current delivery

Analyze sources of and nature of demand

Analyze current Delivery Capability (Demand & Capability analysis)

Model the Service Delivery Workflow

Identify and Define Classes of Services

Design the Kanban System

Evolve and Iterate

Refer to STATIK - Identify and Define Classes of Services

Refer to STATIK - Identify and Define Classes of Services

Evolve and Iterate

Recommended and emerging roles:

SDM - Service Delivery Manager

SRM - Service Request Manager

Team Kanban

*Source - google search


Kanban Cadence

Visibility

Eliminates Overburdening

Reduces multitasking

Shorter lead times

Better Quality

Deferred Commitment

Control or eliminates

interruptions

Does workflow match to team

actual process?

Do you have explicit policies in

place?

Have you implemented WIP

Have you adopted a culture of CI

for all corners

Is there a need for structured

kanban and Continue education

Dissatisfaction

No Delivery in 3 iteration out of 2 months regular

invoices

HIghlighted to our Management with

Trust Deficit

Blind following and Jira to Track purpose and was

unstructured

and Frustration

Remove Delays

Manage Bottlenecks

Improve Economic Cost

1.

2.

3.

persistent determination

http://www.shabdkosh.com/translate/%E0%A4%A7%E0%A5%80%E0%A4%B0%E0%A4%9C/%E0%A4%A7%E0%A5%80%E0%A4%B0%E0%A4%9C-meaning-in-Hindi-Englishhttp://www.shabdkosh.com/translate/%E0%A4%97%E0%A4%AE%E0%A5%8D%E0%A4%AD%E0%A5%80%E0%A4%B0%E0%A4%A4%E0%A4%BE/%E0%A4%97%E0%A4%AE%E0%A5%8D%E0%A4%AD%E0%A5%80%E0%A4%B0%E0%A4%A4%E0%A4%BE-meaning-in-Hindi-Englishhttp://www.shabdkosh.com/translate/%E0%A4%A6%E0%A5%83%E0%A4%A2%E0%A4%BC%E0%A4%A4%E0%A4%BE/%E0%A4%A6%E0%A5%83%E0%A4%A2%E0%A4%BC%E0%A4%A4%E0%A4%BE-meaning-in-Hindi-English

Value 1

- How we will understand and identify blocked lane?

- We wont be able to perform Predictability

- We wont able to get metrics out of the board?

- How we will understand and identify blocked lane?

- We wont be able to perform Predictability

- We wont able to get metrics out of the board?

We cannot have everything in

Doing / In-Progress

No Predictability


DISCOVERY KANBAN DELIVERY KANBAN

To-DoDev IP Peer

ReviewRFQA Testing Re-

OpenQA

Passed

Actual flow:

Done

Confluence

Actionable

Output

Hindi - | |

Meaning - 1. production of a certain amount2. what is produced in a given time period signal that comes out of an electronic system

Outcome

Hindi - |

Meaning - 1. something that results2. phenomenon that follows and is caused by

some previous phenomenon

http://www.shabdkosh.com/translate/%E0%A4%AA%E0%A5%88%E0%A4%A6%E0%A4%BE%E0%A4%B5%E0%A4%BE%E0%A4%B0/%E0%A4%AA%E0%A5%88%E0%A4%A6%E0%A4%BE%E0%A4%B5%E0%A4%BE%E0%A4%B0-meaning-in-Hindi-Englishhttp://www.shabdkosh.com/translate/%E0%A4%89%E0%A4%A4%E0%A5%8D%E0%A4%AA%E0%A4%BE%E0%A4%A6%E0%A4%A8/%E0%A4%89%E0%A4%A4%E0%A5%8D%E0%A4%AA%E0%A4%BE%E0%A4%A6%E0%A4%A8-meaning-in-Hindi-Englishhttp://www.shabdkosh.com/translate/%E0%A4%89%E0%A4%AA%E0%A4%9C/%E0%A4%89%E0%A4%AA%E0%A4%9C-meaning-in-Hindi-Englishhttp://www.shabdkosh.com/translate/%E0%A4%A8%E0%A4%A4%E0%A5%80%E0%A4%9C%E0%A4%BE/%E0%A4%A8%E0%A4%A4%E0%A5%80%E0%A4%9C%E0%A4%BE-meaning-in-Hindi-Englishhttp://www.shabdkosh.com/translate/%E0%A4%AA%E0%A4%B0%E0%A4%BF%E0%A4%A3%E0%A4%BE%E0%A4%AE/%E0%A4%AA%E0%A4%B0%E0%A4%BF%E0%A4%A3%E0%A4%BE%E0%A4%AE-meaning-in-Hindi-English

Ideal Flow

Expected Flow

Data from Live Engagement

Lets have a look on Progress metric

Days >>>>>>>>

# o

f st

ori

es c

om

ple

ted

Taken concepts:

CP1 - Visualize and

CP3 - Manage Flow

Days >>>>>>>>

# o

f st

ori

es c

om

ple

ted

10 20

Days >>>>>>>>

# o

f st

ori

es c

om

ple

ted

10 20

Iteration / Release #1Iteration / Release #2

Days >>>>>>>>

# o

f st

ori

es c

om

ple

ted

10 20

Itera

tion /

Relea

se #1

Itera

tion

/ Rel

ease

#2

Days >>>>>>>>

# o

f st

ori

es c

om

ple

ted

10 20

Itera

tion /

Relea

se #1

Itera

tion

/ Rel

ease

#2

This metric is not a Velocity

Request created

Work delivered

Work In Progress

This starts when we accept order/US (Dev Ready)

Kanban System Lead Time and Cycle Time

Cycle Time:

Cycle Time:

If a team has 32 cards in process and avg. completion rate is 1.25 cards per day

So:

Cycle time = 32 / 1.25 which is = 25.6 days

Problem Statement A: At home, I have 12 bottles of whisky at my bar. I consume and purchase an average of 6 whisky bottles per year. What is the average time each whisky bottle stays in my bar?

Problem Statement B: At home, I have 12 bottles of whisky at my bar. In average, I finish

(and purchase) one whisky bottle every two months. What is the average time each whisky

bottle stays in my bar?


Problem Statement B: At home, I have 12

bottles of whisky at my bar. In average, I

finish (and purchase) one whisky bottle

every two months. What is the average time

each whisky bottle stays in my bar?

Questions:

1. What is the WIP2. What is the Throughput?3. What is the avg. Cycle Time?4. What is the average lead time?


Problem Statement B: At home, I have 12

bottles of whisky at my bar. In average, I

finish (and purchase) one whisky bottle

every two months. What is the average time

each whisky bottle stays in my bar?

Questions:

1. What is the WIP2. What is the Throughput?3. What is the avg. Cycle Time?4. What is the average lead time?

Answers:

Inventory or WIP = 12 (Prob A & B)Throughput is 6 bottles per 12 months (P-A)Average Cycle Time is 2 months (P-B)

Way 1:

WIP = Throughput X Avg. Lead Time

12 bottles = 6 bottles / 12 months * Avg. LT

(12*12)/6 = 24 months is Avg. Lead Time

Way 2:

Avg. Lead Time = WIP X Avg. Cycle Time

Avg, lead time = 12 bottles *2 months/bottle

Avg. Lead Time = 24 months

Iteration / Release Highlights metrics

*source: scaled agile

Self-Assessment Radar Metrics

*source: scaled agile

At present Exploring - Epic Burnup chart with actual SP

A system thinking approach

Concluding thoughts:

Myths & benefits of kanban @ATMs 2nd Meetup_aug05

Presentations & Public Speaking