Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Lesson learned in surviving to Technical Debt

Lesson learned in surviving to Technical Debt

What is Technical Debt? Why should you care? How to tackle it?
These are a couple of lessons learned that I want to share.

Pietro Di Bello

February 01, 2022

More Decks by Pietro Di Bello

Other Decks in Technology


  1. • Long-lived branches • Lack of continuous integration • Long

    build-test cycle • Lack of test environments
  2. • Slow, ineffective tools • Important documentation that is missing

    or out-of-date • Unnecessary documentation that is being maintained and kept up-to- date 📜
  3. Other names for technical debt: • legacy code (valuable code

    that we feel afraid to change 😱) • accidental complication
  4. Technical debt may have a bad influence on • planning

    • morale • defects • delivering visible, working sw at a steady pace
  5. We can live with technical debt, as long as we

    can afford to pay the interest, and as long as the debt doesn’t grow out of control https://blog.crisp.se/2013/10/11/henrikkniberg/good-and-bad-technical-debt
  6. Keep a “tech backlog” and agree on a team policy

    to include at least one of these improvement items in the sprint backlog
  7. Opportunistic refactoring (*) (*) refactoring is a simple, regular process

    of keeping the code clean, easier to understand and easier to change.
  8. Review the De fi nition of Done to include a

    “good scouts rule” 🤞