A Guide to the Project Management Body of Knowledge, Research Paper Example

Every project has a scope, and in most cases, there is no guarantee that the manager in charge of the project will allow changes to be made on the same. The scope spells the reason a project is done, and the objectives intended to be achieved. While the scope may be redefined following an analysis of project progress, the changes recommended should not vary with the original outline.

Some of the circumstances that can lead to deprivation of any changes in the project scope is lack of provision of the same in the change control. Change control is a guide designed at the start of the project outlining how changes in a project will be conducted. In most cases, this guide does not mention anything to do with changes on the project scope (Project Management Institute, 2013). Another circumstance that may lead a customer to be denied change in the scope is because it might be unacceptable and unrealistic. In some cases, the demands to change the project scope might come late into the project. In such cases, the project manager might realize that there is no enough time to enact the requested changes. Prior to the start of a project, a budget is prepared. In the event the budget is too strained to accommodate the request to change the scope, the manager may turn down the request. This is especially the case if at all the changes are touching on the resources.

The best way to handle the customer if the changes to the scope have been denied is to explain in details the impacts of the changes requested towards the project (Project Management Institute, 2013). In some cases, the customer might fail to consider all factors, and in such a situation, the best idea is to let him or her understand all of them. I might advise the customer to establish a clear process of changing the scope, and allow every person to understand it. He or she should be clear on the costs, and time that will be needed for the changes to be effected.

Scope verification addresses the issues on whether every item mentioned in the scope has been considered in the work break structure. Additionally, this stage determines whether the work breakdown structure has mentioned all the items in the WBS. This stage is straight and in most cases, it is done step by step (Project Management Institute, 2013). Change process refers to the step to be followed by a project manager to initiate changes in a given project. The first step of the change process is preparing for the identified change through strategy development, assessment, and preparation. The second step involves management of change through having a detailed change and planning management implementation.

These two processes are needed because through verification, one can confirm that every item mentioned in the scope has a proper WBS to its effect. In short, through verification, the project leader can ensure that nothing has been missed. Through verification, the project leader can ensure there is no superfluous WBS, which might cause problems later in the project (Project Management Institute, 2013). One needs the verification process in order to minimize severe issues that might come up later in the project. Change process is crucial because it ensures that every needed item for the project to commence is vetted thoroughly. Through this process, one can end up cutting on the budget, because it helps one to identify some of the irrelevant issues in the project that can be omitted.

The scope verification process might be initiated in the early stages of the planning process because it is the one that outlines what is intended to be done. The verification should start from the scope statement, moving on to other issues.

Reference

Project Management Institute (2013). A Guide to the Project Management Body of Knowledge: PMBOK Guide. 5^th ed. New York, NY: Project Management Institute, Incorporated.