CAPM Practice: Demonstrate an understanding of business analysis (BA) roles and responsibilities

Scope creep is the gradual, uncontrolled addition of new features or requirements without adjusting constraints. BAs manage this through rigorous change management, requirements baselines, and impact analysis for proposed changes.

**Why not B:** Scope creep refers to the uncontrolled expansion of project scope, not its reduction. Scope shrinking, sometimes called scope erosion, is a different concern where agreed-upon features are quietly removed. Confusing the two reverses the direction of the problem and leads to applying the wrong mitigation strategies.

**Why not C:** Overly detailed documentation is a documentation management issue, not scope creep. Scope creep specifically involves adding new requirements, features, or deliverables beyond the agreed baseline without corresponding adjustments to time, cost, or resources. Verbose documentation does not change what the project delivers.

**Why not D:** Cost overruns are a possible consequence of scope creep but are not the definition of scope creep itself. Costs can exceed budget for many reasons unrelated to scope, such as resource rate increases or estimation errors. Scope creep is specifically about unauthorized or uncontrolled growth in what the project is expected to deliver.