IFO4
Loading...The accumulated cost of suboptimal technical decisions made in the past, expressed as the future engineering effort and operational drag required to remediate. Technical debt is not a balance sheet liability but produces a real efficiency tax on every quarter of operations. The federation requires technical debt to be inventoried with severity, business impact, and remediation effort estimates, with annual reporting tied to the engineering capitalisation register under UFMS-001:2.4(g). Persistent unaddressed high-severity debt is a Tier-2 governance debt indicator.
Coined by Ward Cunningham in 1992 in his metaphor of code shipped quickly being a kind of debt that must be repaid through refactoring.
Federation members maintain a technical debt register inventoried by severity. Annual debt reduction targets are tied to the engineering capitalisation register. Persistent high-severity debt is reported under MEV-Annex:3.2 and reviewed at the steward tier accreditation cycle.
@misc{ifo4_glossary_technical_debt,
title = {{Technical Debt}},
author = {{IFO4 Federation Editorial Board}},
howpublished = {{IFO4 Federation Glossary, slug \texttt{technical-debt}}},
year = {2026},
url = {https://ifo4.org/glossary/technical-debt},
note = {Category: Waste; key: TechnicalDebt}
}Federation members and accredited practitioners may challenge any entry under TGS-002:1.7. Filed challenges are routed to the editorial board, triaged into the revision register, and resolved in writing on the public docket. The slug remains stable through any revision.