A project is implemented using a predictive approach. Unfortunately, a lot of change requests (CR) have been raised. A project manager (PM), who should approve each change request, is overworked…

Approving CRs independently exceeds the BA's authority in a predictive project and violates the change control governance structure that defines who is authorized to approve changes.

Transferring responsibility to the sponsor without restructuring the governance process simply relocates the bottleneck and does not address the root systemic issue with how changes are managed.

Business Analysis Governance defines the decision-making authority, processes, and escalation paths for managing requirements changes; revisiting it allows the BA to propose improvements such as tiered approval thresholds, a change control board, or delegated authority that distributes the approval workload and relieves the PM bottleneck.

Declining CRs solely on the basis of the project approach ignores potentially valid business needs and is not an acceptable change management practice.