fighting the cost monster
DESCRIPTION
Ignite talk presented at Lean-Kanban North America 2013 in Chicago.TRANSCRIPT
![Page 1: Fighting the cost monster](https://reader033.vdocuments.net/reader033/viewer/2022051817/54920962ac795925288b46a8/html5/thumbnails/1.jpg)
FightingFightingThe Cost MonsterThe Cost Monster
an improvement model do deal with software failure demand
Rodrigo Yoshima
![Page 2: Fighting the cost monster](https://reader033.vdocuments.net/reader033/viewer/2022051817/54920962ac795925288b46a8/html5/thumbnails/2.jpg)
Why this Model exists...
Software maintenance costs us $$$$$$$$$$$$
Just like queues, failure demand is deeply hidden
Why not call it technical debt?
It's judgemental and abstract!!!(the problem is both technical and emotional)
![Page 3: Fighting the cost monster](https://reader033.vdocuments.net/reader033/viewer/2022051817/54920962ac795925288b46a8/html5/thumbnails/3.jpg)
What is Failure Demand on this Model?
A Failure Demand is something that happened and the team agrees that should not happen.(and hopefully will take actions to not happen again)
![Page 4: Fighting the cost monster](https://reader033.vdocuments.net/reader033/viewer/2022051817/54920962ac795925288b46a8/html5/thumbnails/4.jpg)
1. No Judgement
The reality is what it is!
Stop exhortation for better practices or zero defects
![Page 5: Fighting the cost monster](https://reader033.vdocuments.net/reader033/viewer/2022051817/54920962ac795925288b46a8/html5/thumbnails/5.jpg)
![Page 6: Fighting the cost monster](https://reader033.vdocuments.net/reader033/viewer/2022051817/54920962ac795925288b46a8/html5/thumbnails/6.jpg)
FAILURE
VALUE
![Page 7: Fighting the cost monster](https://reader033.vdocuments.net/reader033/viewer/2022051817/54920962ac795925288b46a8/html5/thumbnails/7.jpg)
![Page 8: Fighting the cost monster](https://reader033.vdocuments.net/reader033/viewer/2022051817/54920962ac795925288b46a8/html5/thumbnails/8.jpg)
FAILURE DEMAND
65%
Failure Demand x Value Demand Trend
VALUE
Improvement
![Page 9: Fighting the cost monster](https://reader033.vdocuments.net/reader033/viewer/2022051817/54920962ac795925288b46a8/html5/thumbnails/9.jpg)
1. No Judgement2. Visualize Failure Demand
Classify Value x Failure Demand - Decentralized
Measure Value x Failure Trends
Locate where the problem is
![Page 10: Fighting the cost monster](https://reader033.vdocuments.net/reader033/viewer/2022051817/54920962ac795925288b46a8/html5/thumbnails/10.jpg)
![Page 11: Fighting the cost monster](https://reader033.vdocuments.net/reader033/viewer/2022051817/54920962ac795925288b46a8/html5/thumbnails/11.jpg)
1. No Judgement2. Visualize Failure Demand
3. Create Improvement Demand
Analyse the root cause of Failure Demand
Promote meeting to discuss improvement demand
Alocate Kanban capacity to improvement
![Page 12: Fighting the cost monster](https://reader033.vdocuments.net/reader033/viewer/2022051817/54920962ac795925288b46a8/html5/thumbnails/12.jpg)
FAILURE DEMAND
65%
Failure Demand x Value Demand Trend
FAILURE DEMAND
15%
This should convince peopleemotionally.
![Page 13: Fighting the cost monster](https://reader033.vdocuments.net/reader033/viewer/2022051817/54920962ac795925288b46a8/html5/thumbnails/13.jpg)
If you face emotional If you face emotional resistance create a resistance create a system where the system where the problems are visible problems are visible and engage people and engage people emotionally to changeemotionally to change..
David J. AndersonDavid J. Anderson
![Page 14: Fighting the cost monster](https://reader033.vdocuments.net/reader033/viewer/2022051817/54920962ac795925288b46a8/html5/thumbnails/14.jpg)
1. No Judgement2. Visualize Failure Demand3. Create Improvement Demand
Rodrigo Yoshima@rodrigoyTHANK
YOU!