When can changes to requirements occur in a business analysis planning and monitoring assignment?

Restricting changes to before the project scope statement limits change management to only the earliest project phase, which contradicts BABOK guidance on managing requirements throughout the lifecycle.

The BABOK Guide recognizes that business conditions, stakeholder needs, and project circumstances can shift at any point during a project engagement. Requirements changes may be triggered by external events, new stakeholder insights, or evolving technology at any stage. This is why business analysis planning must include change management strategies that apply continuously rather than only during specific phases.

A change control system is a process for evaluating and approving changes, not a starting gate - requirements changes can be initiated at any time and then processed through that system.

Stakeholder approval of requirements does not create a hard cutoff for changes; evolving business needs can necessitate revisiting requirements even after formal approval has been granted.