11. Examplesthis Costs Resulting from Long Cycle Time
I need to know if of
estimate you gave me
last month is still
accurate.
But I workedtime to
I don’t have on that Can you take a
I’ll check with Jim OK. don’t think you by
Yes,I’ll get defect, and
I it’s a it to this
fix it allweeks ago! I’ll
three properly now. look at this? I
when he get’s back. Monday, I’mthison the
I’ve built all in valid
requirement is other
I’ll do a quick fix and
have to read through think it’s a defect.
He’s away for a few weekendtopis it?
stuff more, of it!
any on anyway.
tidy it up later.
the code again.
days.
Project
Manager
Analyst Developer Tester
Knowledge decay
+ increase in the cost of fixing defects
+ reduced quality
+ information becomes stale and needs rework
+ delays accumulate
= reduced customer value
getKanban.com
34. Cycle Time
34
http://www.agileproductdesign.com/downloads/patton_kanban.ppt
35. Kanban Mechanics in a Nutshell
Ready (4) Analysis (2) Development (4) Test (3) Ready to Deployed
Deploy
In Progress Done In Progress Done
10 9 8 5 4 1
11 6 2
12 7 3
13
14
The is testing of Kanban board. downstream ticket 5 process, ticket from as columns. Done the
A ticketan queue may be replenished
WIP we our WIP limit in 1 pushedNoticelimit of when thenew workrepresented it to receive the work. Test,
Because have 2 items in Developmentto its WIP limit we may and indicate thatweis ready deploy. WIP leaving
Now saycompletes Testing, a with a WIPfree, stages ofthere is insufficient the customer. to development limits
Let’sReady stop work being is slot comesWe move3, In Progress now be pulled into Test.
Herelimits exampleticketTest,complete. coversand it so withmay pull aDone, when DevelopmentNotice intoIf on a
the both downstream to from capacity complete
development work on to column names.
ticket, we may beside ticket WIP limit of it cannot be to a ticket into Development from Analysis its WIP limit.
3 parentheses move itthethe Development Done columnpullindicate that it is completed, is already atDone, WIP
inin Development, which has5ais completed,4, so we may “pushed” into Test, because Testwithout breaking aand so
limit.
forth.
Couple questions?Who is working with software development teams?Who is employing Agile Methods?Who is using Scrum?Who is using Kanban?Who has heard of Kanban before?Give aways at the end. Let them choose which class they want a 50% discount on. Random person and who tweets
Many software companies are drowning in a sea of opportunity and instead of focusing on getting the highest value items done we are crippled by trying to do too much at one time.http://www.123rf.com/photo_8127859_single-hand-of-drowning-man-in-sea-asking-for-help.html
3m
What is the impact of change in the left vs the right?Change – underestimatedChange – new high priority requirementWhich plan will have the biggest impact if there is a change?
15 minsTeam breakout then highlights as a group
15 minsTeam breakout then highlights as a group
15 minsTeam breakout then highlights as a group
http://www.123rf.com/photo_7850401_young-male-student-is-overwhelmed-by-way-too-many-homework-assignments.htmlRequestsLack of resourcesDon’t trust that project will ever get started (maybe that is the right business decision)Sr leadership not setting priorities
http://twinpowerment.blogspot.com/
Why waste effort trying to order the input when there is no dependability in the order of delivery? Until this is fixed, management time is better used to focus on improving both the ability to deliver and the predictability of delivery.
Set the rate at which we accept new requirements into our software development pipe to correspond with the rate at which we can deliver working code.Once you balance demand against throughput and limit the work-in-progress within your value stream, magic will happen. Only the bottleneck resources will remain fully loaded. Very quickly, other workers in the value stream will find they have slack capacity. Meanwhile, those working in the bottleneck will be busy, but not swamped. For the first time, perhaps in years, the team will no longer be overloaded and many people will experience something very rare in their careers, the feeling of having time on their hands.Limit WIP in andLevel Flow will:Expose the bottlenecksEnable improvementSimplifies prioritizationWhy waste effort trying to order the input when there is no dependability in the order of delivery? Until this is fixed, management time is better used to focus on improving both the ability to deliver and the predictability of delivery.
Need to throttle the input (demand) into the system
The slack capacity created by the act of limiting work-in-progress and pulling new work only as capacity is available will enable improvement no one thought was possible.By throttling the input (demand) into the systemThis will limit the Work In Progress and Level Flow Which will expose the bottlenecksAnd enable improvementOnce you balance demand against throughput and limit the work-in-progress within your value stream, magic will happen. Only the bottleneck resources will remain fully loaded. Very quickly, other workers in the value stream will find they have slack capacity. Meanwhile, those working in the bottleneck will be busy, but not swamped. For the first time, perhaps in years, the team will no longer be overloaded and many people will experience something very rare in their careers, the feeling of having time on their hands.Limit WIP in andLevel Flow will:Expose the bottlenecksEnable improvementSimplifies prioritizationWhy waste effort trying to order the input when there is no dependability in the order of delivery? Until this is fixed, management time is better used to focus on improving both the ability to deliver and the predictability of delivery.
Buy a Feature
Does this feel like the dev process? Dev and QA?
Do we ever have any built up queue in front of QA?Gets continually slower
Slow down A to 5 items/ min (reduce Dev resources)Put B before A Double B Resources (hire more QA)Reallocate resources from A to B to level the flow (TDD or Dev help QA?)
Prioritization is no longer about ordering all the WIP or all initiatives but picking the next one as one finishes
看板 kan · ban [kahn-bahn] noun,Kanban literally means “visual card,” “signboard,” or “billboard”Kanban software development is the application of lean manufacturing principles and practices to software development
Draw Agile and Lean circles overlapping with influencesLean – PDCA, Kaizen culture, Deming, PDCA, Limit Waste, Focus on ValueAgile – Empirical, self organizing teams, Focus on Working Software, quick feedback, incremental development
It requires that some process is already in place so that Kanban can be applied to incrementally change the underlying process.The essence of starting with Kanban is to change as little as possible.
The organization (or team) must agree that their current circumstances warrant a gentle, evolutionary approach to improvement. Perhaps a sweeping engineered change has recently failed due to resistance from team members, or perhaps the politics of the organization make it too risky for managers to propose and implement sweeping changes? Without agreement that a slow, gentle, evolutionary, incremental approach is the right way forward then there won’t be the right environment or management support for a Kanban initiative.
draw card walls to show the activities that happen to the work rather than specific functions or job descriptions.The first school of thought says do not try to second-guess the location of bottleneck or the source of variability that will require a buffer. Rather, implement the system and wait for the bottleneck to reveal itself, then make changes to introduce a buffer. A variant on this suggests that WIP limits should be set
Reduce the number of Kanban slots allowed until cycle time remains unchangedReduce the size of development itemsWork in progress is actually the number of items * the average size of itemsIdentify and act on bottlenecks immediatelyRelieve repeated bottlenecks by changing the number and types of people in each role and cross training
Couple questions?Who is working with software development teams?Who is employing Agile Methods?Who is using Scrum?Who is using Kanban?Who has heard of Kanban before?Give aways at the end. Let them choose which class they want a 50% discount on. Random person and who tweets