2. 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)
3. 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)
4. 1. No Judgement
The reality is what it is!
Stop exhortation for better practices or zero
defects
9. 1. No Judgement
2. Visualize Failure Demand
Classify Value x Failure Demand - Decentralized
Measure Value x Failure Trends
Locate where the problem is
10.
11. 1. No Judgement
2. 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
13. If you face emotionalIf you face emotional
resistance create aresistance create a
system where thesystem where the
problems are visibleproblems are visible
and engage peopleand engage people
emotionally to changeemotionally to change..
David J. AndersonDavid J. Anderson