Download as PDF, PPTX
Uploaded byJez Halford
Seven deadly wastes
The document outlines the 'seven deadly wastes' in software development, which include transport, inventory, motion, waiting, over-processing, over-production, and defects. It emphasizes the importance of reducing these wastes to enhance efficiency, advocating for practices like continuous integration, automation, and prioritizing working code. The author provides strategies to address each waste, such as visualizing work in progress and focusing on delivering features frequently.
More Related Content
Seven deadly wastes
- 1.
- 2. Jez Halford Software DevelopmentConsultant I help software teams to go faster @jezhalford jezhalford.com medium.com/@jezhalford
- 3. What slows youdown?
- 4.
- 5.
- 7.
- 8. 1 “Transport” ● Handovers betweenteams or developers ● Bouncing back and forth between Dev and QA teams ● Deploying to different environments Movement of the work
- 9. 1 “Transport” ● Pairing andcollaboration ● Continuous Integration ● AutomationMovement of the work
- 11.
- 12. 2 “Inventory” ● Abandoned Work ●Work In Progress ● Working on several things at once Undelivered work
- 13. 2 “Inventory” ● Reduce yourlead time ○ Feature toggles ○ Smaller deliverable units ○ Branch by abstraction ● Visualise your work in progress ● Stop starting and start finishing Undelivered work
- 14.
- 16.
- 17. 3 “Motion” ● Task switching ●Irregular meetings ● Hot desking ● Building new environments Movement of people around the work
- 18. “Motion” ● Reducing inventoryalso reduces motion ● Get Rhythm! Movement of people around the work
- 20.
- 21. 4 “Waiting” ● Waiting forother teams ● Waiting for outside input ● Waiting for clarificationDelays in delivering the work
- 22. 4 “Waiting” ● Consider thewhole system ● Take ownership ● Talk to peopleDelays in delivering the work
- 24.
- 25. 5 “Over Processing” ● Goldplating ● Solving imaginary scaling issues ● Writing “libraries” instead of operational code Working too hard
- 26. “Over Processing” ● Deliveroften ● Base performance improvements on evidence ● Refactor when you need to Working too hard
- 28.
- 29. 6 “Over Production” ● 64%of built software features are rarely or never used* ● Every feature has a cost ● Developing useless features is doubly wasteful Doing useless work * From a limited study in 2002 - probably nonsense
- 30. 6 “Over Production” ● Strongproduct ownership ● Fast feedback ● Remove stuff that isn’t usedDoing useless work
- 32.
- 33. 7 “Defects” ● Bugs inproduction are bad ● Bugs before production are still bad Working on the work
- 34. 7 “Defects” ● Automated tests ●Dev/Prod parity ● Continuous integration ● Shared understanding ○ Example mapping ○ OOPSI ○ BDD Working on the work
- 35.
- 36. ● Ship smallthings often ● Automate everything you can ● Work on one thing at a time ● Maintain a regular pace ● Deal with problems and complexity early ● Prioritise working code over perfect code Transport Inventory Motion Waiting Over Processing Over Production Defects
- 37.