fighting the cost monster

FightingFightingThe Cost MonsterThe Cost Monster

an improvement model do deal with software failure demand

Rodrigo Yoshima

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)

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)

1. No Judgement

The reality is what it is!

Stop exhortation for better practices or zero defects

FAILURE

VALUE

FAILURE DEMAND

65%

Failure Demand x Value Demand Trend

VALUE

Improvement

1. No Judgement2. Visualize Failure Demand

Classify Value x Failure Demand - Decentralized

Measure Value x Failure Trends

Locate where the problem is

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

FAILURE DEMAND

65%

Failure Demand x Value Demand Trend

FAILURE DEMAND

15%

This should convince peopleemotionally.

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

1. No Judgement2. Visualize Failure Demand3. Create Improvement Demand

Rodrigo Yoshima@rodrigoyTHANK

YOU!