CAPM Practice: Validate requirements through product delivery

Delivery-based learning often reveals requirements gaps significant enough to warrant re-baselining. When this occurs, the BA updates requirements, conducts impact analysis, obtains stakeholder agreement on the revised baseline, and ensures the team understands the changes before planning next delivery.

**Why not A:** Requirements are living documents that must evolve as new information emerges. Refusing to update a baseline after discovering significant gaps would lock the project into delivering functionality that does not meet actual user needs. The BABOK and standard practice explicitly support controlled re-baselining when justified by validated gaps.

**Why not B:** Re-baselining is a collaborative decision driven by evidence of misalignment between delivered functionality and stakeholder needs, not a unilateral action triggered solely by a project manager's request. Waiting for a single role to initiate the process ignores the BA's responsibility to surface gaps discovered through validation activities.

**Why not C:** Limiting re-baselining to fixed quarterly cycles is arbitrary and risks prolonged delivery of misaligned functionality. When significant gaps are discovered, the impact should be assessed and the baseline updated promptly through the project's change control process, regardless of where the organization is in its planning calendar.