Question

You have now completed the charter for your website cloud migration. The project sponsor wants to expand the scope of the project, but you are hesitant to do so per the constraints in place. Discuss why increasing the scope of this project is not a good idea. If you must increase scope, what additional considerations (costs and timeline) must be given to accomplish this scope change?

Answer 1

Discuss why increasing the scope of this project is not a good idea.

It is not a good idea to have the increased scope of the project as the project has a tight deadline and requirement for the project charter. In a project scope, we try to figure out the different words which are to be accomplished in a project and in order to fulfill the desired work, different resources are allocated. It is expected that the Sponsor must understand the fact that project scope has already been finished and any request for change will be very hard to accommodate. This is termed as scope creep in which the stakeholders try to include more activities or goals in a project without allocating additional budget, deadline or schedule which will make impossible for the project to be completed within the deadline. If the different objectives and tasks are to be addressed, it will require re-negotiation of the project with the stakeholders for resources and more time. It is not possible to satisfy each and every individual but being the project manager the main task is to find the best balance which can satisfy the project requirements.

If you must increase the scope, what additional considerations (i.e., costs, timeline) must be given to accomplish this scope change?

In order to consider additional time, cost and performance, we will require work breakdown structure (WBS) and it has to be signed off by the project stakeholders. In the case of project scope creep, the requirements and priorities are changes and thus more time and resources will be needed.