CAPM Practice: Determine how project methodologies influence business analysis processes

Requirements debt accumulates when requirements are insufficiently specified, conflicts are deferred, or stakeholder needs are not fully discovered. Like technical debt, it compounds — poor requirements lead to wrong implementation, which leads to rework, which leads to schedule pressure, which leads to more requirement shortcuts.

**Why not B:** Requirements debt is not a positive measure. Like technical debt, it represents accumulated problems — poorly specified, ambiguous, or undiscovered requirements — that compound over time and increase rework costs. It is a liability, not a planned asset.

**Why not C:** Requirements debt is not the financial cost of outstanding changes. It refers to the accumulated quality deficit in requirements specification — ambiguities, conflicts, and gaps — that creates compounding problems as development builds on weak requirements foundations.

**Why not D:** Requirements debt can accumulate even when requirements are formally documented. Poorly written, ambiguous, or conflicting documented requirements still constitute requirements debt. The issue is quality and completeness, not merely whether documentation exists.