Technical Debt Paydown

A shared definition, a scored debt register, an agreed capacity share and the weekly and monthly routines that pay debt down steadily, for engineers, teams and managers.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Technical Debt Paydown, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

⚙️ Software Engineering

Technical Debt Paydown

Identifying, prioritising and steadily paying down technical debt so the codebase stays changeable without stopping feature work.

  1. Shared definition of technical debt for the team
  2. Technical debt register in the issue tracker
  3. First debt inventory in a one-hour team session
  4. Change hotspot map from version control history
  5. Cost of debt estimate in engineer hours
  6. Debt ticket template and labels
  7. Baseline of code health indicators
  8. Agreed capacity share for debt work
  9. Debt scoring rubric for impact and effort
  10. Weekly debt triage of new register entries
  11. Monthly debt review with the product manager
  12. Boy scout rule in everyday pull requests
  13. Quarterly debt paydown plan
  14. Debt interest log during feature work
  15. Monthly code health dashboard update
  16. TODO and FIXME comment sweep
  17. Feature flag retirement routine
  18. Dead code and unused endpoint removal
  19. Rotating debt owner each sprint
  20. Learning the technical debt quadrant
  21. Reading list on working with legacy code
  22. Characterisation tests before touching debt
  23. Code health metrics that predict pain
  24. Explaining debt to non-engineers in business terms
  25. Recognising architecture-level debt
  26. Small refactoring moves practised on katas
  27. Business case for a major debt item
  28. Fix, contain or accept decision for the top ten
  29. Choosing a code health analysis tool
  30. Debt funding model comparison
  31. Sunsetting a little-used feature to delete its code
  32. Consolidating duplicate implementations
  33. Test debt paydown in the riskiest module
  34. Configuration and environment variable cleanup
  35. Unused database columns and tables removal
  36. Fix-it week for the debt register
  37. Debt retrospective after a major release
  38. Annual debt review for engineering leadership
  39. Paydown before a planned launch or scale-up
  40. Debt handover when an engineer leaves
  41. Inheriting a codebase as a new tech lead
  42. Debt plan for an early-stage team after first launch
  43. Debt paydown in a team of one or two
  44. Debt alignment after a team merger or acquisition
  45. Protecting debt capacity under deadline pressure
  46. Taking agency-built code in-house
  47. Debt fitness functions in the pipeline
  48. Ratcheting down suppressed warnings and type errors
  49. Debt portfolio view across several teams
  50. Measuring the delivery impact of paydown

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Shared definition of technical debt for the team

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Ask five engineers what counts as technical debt and you get five answers: ugly code, missing tests, an old framework, a product decision someone dislikes.

First tasks

  • Ask three teammates for one example each of debt that slowed them down this month
  • Ask the agent to draft a one-page definition from those examples
  • List five things the team should not log as debt, such as bugs and feature requests
  • Agree the wording at the next team meeting and link it from the README

Technical debt register in the issue tracker

Debt that lives only in people's heads leaves the company when they do, and debt scattered across chat threads and code comments can never be prioritised. One register in the tool the team already uses, with a consistent set of fields, turns complaints into items that can be scored, scheduled and closed. A register in a separate spreadsheet tends to die within a quarter, so put it where the work happens.

First tasks

  • Create a debt label or issue type in the team's tracker
  • Agree the five required fields for every debt item
  • Move twenty existing debt notes and tickets into the register
  • Merge or close register entries that duplicate or no longer apply @recurring(monthly:28)

First debt inventory in a one-hour team session

Putting the team in a room for an hour and asking where the codebase hurts is the quickest way to populate a register. Silent writing first, then grouping, surfaces the debt that everyone works around but nobody has written down. The output is raw, but it gives the register its first real shape within a fortnight of starting.

First tasks

  • Book a one-hour session with every engineer on the team
  • Prepare a shared board with columns for testing, coupling, tooling, data and other
  • Run ten minutes of silent writing before any discussion
  • Enter every item into the register within two days

Make it yours.

Install Technical Debt Paydown, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.