Your SlideShare is downloading. ×
Fighting the cost monster
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Fighting the cost monster

499
views

Published on

Ignite talk presented at Lean-Kanban North America 2013 in Chicago.

Ignite talk presented at Lean-Kanban North America 2013 in Chicago.

Published in: Business, Technology

0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
499
On Slideshare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
7
Comments
0
Likes
4
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. FightingFightingThe Cost MonsterThe Cost Monsteran improvement model do dealwith software failure demandRodrigo Yoshima
  • 2. Why this Model exists...Software maintenance costs us $$$$$$$$$$$$Just like queues, failure demand is deeplyhiddenWhy not call it technical debt?Its judgemental and abstract!!!(the problem is both technical and emotional)
  • 3. What is Failure Demand on thisModel?A Failure Demand is something that happenedand 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 zerodefects
  • 5. FAILUREVALUE
  • 6. FAILURE DEMAND65%Failure Demand x Value Demand TrendVALUEImprovement
  • 7. 1. No Judgement2. Visualize Failure DemandClassify Value x Failure Demand - DecentralizedMeasure Value x Failure TrendsLocate where the problem is
  • 8. 1. No Judgement2. Visualize Failure Demand3. Create Improvement DemandAnalyse the root cause of Failure DemandPromote meeting to discuss improvement demandAlocate Kanban capacity to improvement
  • 9. FAILURE DEMAND65%Failure Demand x Value Demand TrendFAILURE DEMAND15%This should convince peopleemotionally.
  • 10. If you face emotionalIf you face emotionalresistance create aresistance create asystem where thesystem where theproblems are visibleproblems are visibleand engage peopleand engage peopleemotionally to changeemotionally to change..David J. AndersonDavid J. Anderson
  • 11. 1. No Judgement2. Visualize Failure Demand3. Create Improvement DemandRodrigo Yoshima@rodrigoyTHANKYOU!