You have completed the requirements documentation and the stakeholders have signed off on the requirements. Now the requirements are advancing into a project as your organization has chartered a…

The project sponsor authorizes and funds the project but is not responsible for the technical assessment of solution scope to define project scope.

The project manager is responsible for defining and managing project scope once a project has been formally chartered. After the business analyst completes requirements documentation and stakeholders sign off, the project manager assesses the solution scope to determine what work is needed - this becomes the project scope, governed by the scope management plan.

The business analyst defines solution scope during requirements development, but once the project is chartered, scope assessment responsibility transfers to the project manager.

Key stakeholders provide input and approval on requirements but do not hold formal responsibility for assessing solution scope to determine project scope.