CAPM Practice: Determine how project methodologies influence business analysis processes

Predictive scope cuts require formal change control and impact analysis. Adaptive projects manage scope reduction naturally through backlog prioritization — the team always works on the highest-priority items, so running out of time means lower-priority items are not done rather than requiring formal scope reduction processes.

**Why not B:** Scope is regularly managed in adaptive projects through backlog prioritization. Lower-priority items naturally fall off when time runs out. Agile explicitly embraces scope flexibility as one of its core principles — scope is the most commonly adjusted constraint.

**Why not C:** Scope cutting processes differ significantly between methodologies. Predictive projects require formal change control and CCB approval, while adaptive projects use backlog reprioritization. The formality and mechanisms are fundamentally different.

**Why not D:** BAs play an important role in scope decisions regardless of methodology. In predictive projects, BAs perform impact analysis for change requests. In adaptive projects, BAs help the product owner prioritize the backlog. Scope cuts are not made by the development team alone.