Upload
maris-prabhakaran-m
View
112
Download
0
Embed Size (px)
Citation preview
KANBANIN ACTION
AGILE VIETNAM MEETUP
M.MARIS PRABHAKARAN
Sun Certified Enterprise Architect(SCEA)
GET KANBAN Board GameCreator Russhel Healey
FEATUREBAN Creator - Mike Burrows
Kanban in Action
@ SCB Bangkok MEETUP@ BARCLAYS MEETUP SINGAPORE@ Live Agile workshop Singapore@ Chennai Agile Meet India
KANBAN
Our challenges Demand and capacity are not
balanced
Quality issues
Changing priorities
Work doesn’t flow, it takes a while to get things done
What we would like to achieve
Smoother and faster flow of work (shorter lead time)
Better predictability
Higher quality
Continuous improvement
Sustainability
Kanban principles & Practices
Kanban core practicesVisualise the
workflow
Limit WIP
Make process policies explicit
Manage flow
Feedback Loops
Improve & Evolve
Control chart (Lead time)
Suggestions:• Lead time/type of work item (feature, support request, expedite…)• Lead time/size of work item (S, M, L, XL…)
Mean
80% confidence interval
Lead time
Lead time
Cumulated flow diagram
Cycle time
Lead time
WIP
Incoming size
Analysis
TestDevelopment
Done
TodoRemaining
work
Look for patterns
StepsBubbleStarvationPlateau
Questions?Learn from Get kanban board
Questions?Debrief
Several different events took place during the course of the game. Can you see the effects of these on the charts? Can you see immediate impact? Can you see longer lasting effects? What are they?
What other kinds of information can be seen on the charts? WIP, cycle time, velocity/throughput, trends, outliers?
What is the relationship between WIP and cycle time on the CFD, and how did WIP and cycle time change through the course of the game?
Given our knowledge of cycle time from the Control Chart, if we were asked to provide an SLA for Standard stories with 90% confidence, what would a reasonable target cycle time be?
What were the (opportunity) cost of delay curves for the two Fixed Delivery Date stories?
What about the other stories? Did people begin to consider the whole value stream, rather than just one little part of it? Is this a good thing?
Questions?Debrief
Were dice able to be played mainly in their areas of specialization? Is this a good thing?
Did people begin to think in terms of “pull” from the right? Is this the way we usually think about our work?
Did we see “swarming” happening in the game? When did it happen? Was it effective?
Was the work visualized and the status of work readily apparent?
What policies were made explicit? Did these help to streamline discussion?
Questions?Thank you
Maris Prabhakaran .Mhttps://in.linkedin.com/in/[email protected]
Why Kanban?
I want to see the work in Progress and know the status of each work item
I want to see the bottlenecks
I want to reduce the lead time
I want to improve the predictability
I want to work in a more Agile way
I work on many different type of work items, with changing priorities and interruptions
I want to manage many projects with a pool of resources
I want to do just in time prioritization
I want to improve my process
WIP limits• Adjust demand to capacity• Pull system• Stop starting, start finishing• Eliminate waste
Lead time, WIP and throughput
Continuous improvement
JIT (just in time)
Start where you are!
WHY HOW
Source: http://3.bp.blogspot.com/-DBZTt579wKA/Twng733BptI/AAAAAAAAALQ/DWKmVU8sXgw/s1600/process-prescription.jpg
Kanban vs other methods