Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Delivering technical debt

Whether we know it or not, every time we deliver a feature we also deliver technical debt. This debt remains largely invisible, it isn't tracked, it isn't visible on our information radiators and we very seldom tell our clients about it. The closest we come to acknowledging technical debt is bugs, mainly because our users tell us there is a problem, so we can't ignore it. Technical debt shouldn't be invisible, it's as real as the features we deliver and we should start treating it so. In this talk I propose a technical debt model which can be used when identifying technical debt, furthermore I propose a low friction technique for integrating technical debt into your current SDLC process.

  • Login to see the comments

  • Be the first to like this

Delivering technical debt

  1. 1. Delivering Technical Debt Brendon Page
  2. 2. Me twitter @brendonpaginate Software Developer @ Chillisoft
  3. 3. Overview • Origin • Types • Delivering
  4. 4. The Origin Story “Shipping first time code is like going into debt. A little debt speeds development so long as it is paid back promptly with a rewrite.” “Every minute spent on not-quite-right code counts as interest on the debt”
  5. 5. Good Metaphor It stuck
  6. 6. Metaphor Clarification Explain Refactoring
  7. 7. Powerful Metaphor Think & Reason about Re-work
  8. 8. Types Reckless Prudent Deliberate Inadvertent We don’t have time for design We must ship now and deal with the consequences What’s layering? Now we know how we should have done it Responsibility Awareness 10 Features 1 Week Deadline Amount of debt
  9. 9. What normally happens Work All the information Unique position to identify technical debt
  10. 10. Technical debt is real
  11. 11. What should happen Work Talk about it Classify it
  12. 12. Hope Lean manufacturing
  13. 13. Implementing Red Bin
  14. 14. The Red Bin Feature 2 Red Bin 3 Red Bin Backlog Queue WIP Done During the course of the day During the stand up the next day
  15. 15. Deliver debt like a feature Red Bin Backlog Queue WIP Done Feature 2 End of the sprint
  16. 16. Summary
  17. 17. Thank you! Questions?