CAPM Practice: Validate requirements through product delivery

Requirements retire when business conditions change, making them irrelevant. A market shift, regulatory change, or better solution may make a previously prioritized requirement unnecessary. Formally retiring obsolete requirements prevents teams from building things that are no longer needed.

**Why not A:** Removing poorly written requirements from the backlog is requirements cleanup or grooming, not retirement. Requirements retirement specifically refers to formally retiring previously valid requirements that have become obsolete due to changing business conditions, technology, or better solutions.

**Why not C:** A scheduled archival at project close is project documentation archiving, not requirements retirement. Requirements retirement can happen at any point during the project lifecycle when business conditions change, not only at project closure.

**Why not D:** When business analysts retire and transfer knowledge, that is personnel succession planning, not requirements retirement. Requirements retirement is about the lifecycle of individual requirements becoming obsolete, not about BA staff transitions.