Technical Debt Inventory and Attributes

The relationship between the Technical Debt Inventory and the Projects Inventory is one of consumption and cross-reference. The Technical Debt Inventory consumes Project identifiers, ownership, funding, schedules, milestones, dependencies, and outcome context when a Project remediates, reduces, retires, or otherwise treats Technical Debt. The Projects Inventory remains authoritative for Project delivery; the Technical Debt Inventory remains authoritative for the debt obligation, treatment decision, validation criteria, residual debt, and closure. A dedicated related inventory is not present in the supplied IF4IT URL inventory. Until one is published, refer to the IF4IT Enterprise Inventory Management Best Practices document for the current Noun Type definition and inventory-governance context.

The relationship is carried through these attributes: Related Projects and Initiatives [Multi-Value]; Related Project; Remediation Plan Reference; Funding Source; Funding Status; Approved Funding; Remediation Milestones [Multi-Value]; Remediation Dependencies and Prerequisites [Multi-Value]; Target Start Date; Target Completion Date; Target Outcomes [Multi-Value]. The related inventory’s stable Semantic Identifier or other authoritative identifier should be stored rather than duplicating the full related record. Changes that affect materiality, priority, acceptance, remediation, validation, closure, or reopening should be reconciled across both records while preserving each inventory’s separate audit history.

This relationship connects debt decisions to funded execution and allows governance forums to see which Projects address which obligations, whether milestones are credible, and whether Project completion actually produced validated debt outcomes. Without it, Technical Debt may be approved but never scheduled, Projects may claim benefits without resolving the condition, and closure may be inferred from Project status rather than evidence.