CAPM Practice: Determine how project methodologies influence business analysis processes

Progressive elaboration means adding detail to requirements at the right time — when they're about to be implemented. Far-future items are kept coarse (epics, themes); items approaching development are refined into detailed, testable stories. This avoids wasting effort on details that may change.

**Why not A:** A formal review conducted by a project sponsor is a governance or approval activity, not elaboration. Elaboration is a continuous, iterative process carried out by the team as backlog items move toward implementation — it is not a single event led by a sponsor, and it does not require formal sign-off to occur.

**Why not B:** Agile explicitly avoids producing comprehensive requirements documents upfront because of the waste involved in detailing requirements that may change. Producing an elaborate requirements document at the start of an agile project contradicts the principle of progressive elaboration, which intentionally defers detail until it is needed and unlikely to change.

**Why not D:** Simplifying or eliminating redundant requirements is a requirements rationalization or consolidation activity, not elaboration. Elaboration means adding detail and specificity to requirements over time — it is an expansive process that makes requirements more concrete, not a reductive process that makes them fewer or simpler.