Connect debt to a product goal or constraint

Describe the work that debt makes slower or riskier, using a recent example. Product owners can evaluate a proposed intervention more easily when it enables a planned capability or reduces a recurring failure. Avoid presenting debt as a separate technical wish list with no relation to product outcomes.

Illustrative scenario: a planned subscription change requires touching duplicated rules across several modules. Put a bounded policy-boundary improvement alongside that feature's planning. Explain which behavior stays stable and how the improved structure will support the new rule without claiming an unsupported velocity increase.

Make quality and acceptance explicit

Use the team's Definition of Done to make required quality checks visible for new increments. Debt items still need their own acceptance conditions, such as a clear responsibility boundary and passing regression evidence. Do not use the label technical work to bypass review or leave the result untestable.

Separate an exploratory task from an implementation commitment when dependencies or behavior are unknown. A short investigation can produce a map, risks, and an estimate range. This gives planning useful information without pretending that a complex architectural cleanup is a fully understood story before anyone examines it.

Inspect capacity choices and results

Choose capacity based on impact, upcoming changes, incidents, and uncertainty. Make the consequence visible when urgent product work displaces an accepted debt intervention. A fixed percentage can be a local planning convention, but it does not by itself identify the highest-value work or guarantee that debt decreases.

Use retrospectives and planning reviews to inspect recurring sources of debt and the outcomes of completed interventions. If the same rushed decision repeatedly creates rework, improve how the team handles that constraint. Keep the discussion focused on decisions and system conditions rather than assigning blame to individuals.

Working sheet

Debt in an Agile workflow
MomentUseful actionEvidence
RefinementExplain affected upcoming workConcrete dependency or change example
PlanningChoose bounded interventionAcceptance condition and owner
ImplementationPreserve quality requirementsReviewed change and relevant checks
ReviewInspect resulting capabilityOriginal constraint demonstrably improved
RetrospectiveExamine recurring debt creationAgreed process adjustment
Download this worksheet (CSV)

Questions about make technical debt visible in Agile delivery

Does Scrum require a technical debt sprint?

The Scrum Guide does not prescribe a special debt sprint. Plan the work transparently using the team's product and quality responsibilities.

Can debt work be part of a feature?

Yes, when it directly enables the feature and remains explicit enough to review and verify. Keep acceptance conditions clear.

How should I use the working sheet?

Download the CSV and replace the sample rows with evidence from your repository. Record a clear acceptance check and an owner for each item. Keep unresolved assumptions visible rather than treating the example as a completed assessment.

Sources and further reading

Examples are illustrative. They are not customer results, security guarantees, or a substitute for checking the documentation for your installed version.

Make the next change verifiable.

Getzilla is an open source workflow for changes to existing repositories. Inspect the project, define acceptance checks, and keep independent review in the loop.

See the repository workflow See current access and pricing