kanban - the gateway to total improvement
DESCRIPTION
Techniques to add to a kan-ban software development environment to keep improvingTRANSCRIPT
Kan-‐Ban The Gateway Drug
Stuff to talk about • Gemba walk • Value Stream Mapping • Eli Goldrat Theory of Constraints • Work cell design (pairing) • AutonomaGon • Single-‐Minute Exchange of Die • Kaizen • Just in Time • Plan Do Check Act (PDCA) • Total ProducGve Maintenance • Etc, etc.
Who is using Kan-‐Ban? • How do we improve it?
– Remove cards! • Why would we remove cards?
– Eliminate WIP • Why would we eliminate WIP?
– To increase throughput • Why would we increase throughput?
– To get working code faster than right now • Why do we want working code faster?
– To see if it is really the right working soTware • Why do we want to get the right soTware?
– So we stay in business…
GEMBA WALK
Gemba Walk
• Gemba – the place that maWers most
But seriously…Who Should Do This?
• Leadership – VP’s – Directors – Managers – CxO’s
Go See
• Is the process aligned with the purpose?
• Are people engaged?
• Does the process support them?
Ask Why
• Opportunity – look for symptoms rather than prescribing soluGons
• Waste – eliminate redundancies, overproducGon, and others of the eight wastes
• Problem – confirm what we are trying to achieve and why can’t we?
Show Respect
• Respect people • Rely on people • Develop People • Challenge People
Champion Change
• If you see it, you own it • Do this frequently – It will be painful at first – for everybody
• Encourage others to join you – Especially your manager…
• Don’t make plans in a vacuum – Solicit the help of the people on the team – Have them suggest ideas, make changes to problems you observe
EX
ER
CIS
E • Think about your workplace
• Go for a “virtual walk” to one of your team areas
• What is on the wall – anything? • Is this useful? • Are the desks arranged in a way conducive to collaboraGon?
• What communicaGon tools do you see?
• What is the level of noise – especially informal chaWer?
VALUE STREAM MAPPING
• Method to document the process flow • IdenGfy value added acGviGes • IdenGfy waste – WaiGng, inventory, transportaGon, etc.
Put story on Kan-‐ban board
Analysis
Wait Wait
Explain to developer
Dev gets story
Code and unit test
QA test Add to build
Wait / Transport to meeGng room
Wait Wait
1 min
2 days
2 hrs
1 day
2 mins
2 hrs
20 mins
2 mins
Transport to dev’s cubicle
4 hrs
1 day 5 days
2 hrs 20 mins
Efficiency -‐ Value Add -‐ 523 mins / total Gme -‐ 4,442 = 12%
OMG – really?
• Yep…really • Things to look for – WaiGng Gme (of course) – Are all “value add” acGviGes really value add? – Sequence of events – LocaGons ( do you need a meeGng room?)
EX
ER
CIS
E • In your table groups, draw a Value
Stream Map for the registraGon process today – Start at the moment you entered the parking lot
– End when the first session you aWended got under way
– Make up the Gmes – I know you were not recording them!
– How much value-‐add Gme was there? – What could you do differently to eliminate NVA Gme?
Let’s have a meeGng – next Friday OK? Friday… Everybody here? Great. Sure, we can wait unGl she is back from vacaGon… 2 weeks later… How should we add this feature? Oh, what feature? Let’s talk about that….. Hey, did we ask our customer yet? Much, much later… Well, there it is. Can we get this in producGon by tomorrow?
Value add 7me = minutes / total 7me = months
WORK CELL DESIGN
OK, not really, but…
• How does your team work together • …or does it?
As an online banking customer, I want to be able to monitor my daily balance so that I never over-‐spend my account.
2
Swarming
Big Room Planning
EX
ER
CIS
E • In your table group, discuss how you
might apply this to your teams – Will it work? – What could limit its effect? – What sort of changes would you need to make?
– Do you have remote teams? – What can you do to eliminate independent teams?
THEORY OF CONSTRAINTS
Singular Focus ..or “Focus and Finish”
Value realizaGon
EX
ER
CIS
E • Find a partner
• “A” needs a pen and paper, “B” needs a watch or Gmer
• A -‐ write the numbers from 1 to 26 on the card
• B – Gme how long this takes • A – write the leWers a through z on the card • B – Gme how long this takes • A – write them both together thus: – a b c d e ……y z – 1 2 3 4 5 25 26
• BUT – write a -‐1, b-‐2, etc. alternaGng between leWers and numbers
• B – Gme how long this takes
• GEMBA walk • Value Stream mapping • Work cell design (pairing to extremes) • Theory of Constraints