CAPM Practice: Determine how project methodologies influence business analysis processes

In waterfall, requirements changes go through a formal change control process (change request, impact analysis, CCB approval). In agile, changes are welcomed — new requirements are added to the backlog and prioritized accordingly, without bureaucratic approval for most changes.

**Why not B:** Agile methodologies are not more formal in their change control processes than waterfall. In fact, agile embraces change as a natural part of development through iterative planning and backlog refinement. Waterfall typically requires more formal change control boards and documented change requests because changes late in a sequential lifecycle are costlier to implement.

**Why not C:** Change control is required in both waterfall and agile methodologies, though it manifests differently. In waterfall, formal change request processes govern scope modifications after baselines are set. In agile, change is managed through backlog prioritization, sprint planning, and product owner decisions—it is still controlled, just through different mechanisms.

**Why not D:** Waterfall and agile do not use identical change control processes. Waterfall relies on formal change control boards, documented impact assessments, and baseline comparisons. Agile manages change through iterative cycles, continuous reprioritization, and close stakeholder collaboration, making the two approaches fundamentally different in their mechanics.