Scope Management Plan

Here is a Scope Management Plan template:

1. Introduction

The purpose of this document is to define the process and procedures for managing the scope of the project. The scope of the project is the work that needs to be done in order to deliver the project objectives.

2. Project Overview

Provide a brief overview of the project, including its purpose and objectives, the stakeholders involved, and any other relevant information.

3. Scope Planning

3.1 Define the project scope

The project scope will be defined by identifying the specific deliverables, objectives, and requirements that must be met in order to successfully complete the project.

3.2 Create a scope management plan

A scope management plan will be created to outline the process and procedures for managing the scope of the project. The scope management plan will identify the roles and responsibilities of the project team and stakeholders, the process for controlling scope changes, and the tools and techniques that will be used to manage the project scope.

3.3 Identify project deliverables

All project deliverables will be identified and documented. Deliverables may include products, services, or other outcomes that are required in order to complete the project successfully.

3.4 Identify project constraints

All project constraints, including time, budget, and resources, will be identified and documented. The project team will work within these constraints to ensure that the project is completed on time, within budget, and to the required quality standards.

4. Scope Definition

4.1 Create a Work Breakdown Structure (WBS)

A Work Breakdown Structure (WBS) will be created to decompose the project scope into smaller, more manageable tasks. The WBS will provide a hierarchical breakdown of the project work, making it easier to manage and control.

4.2 Define task dependencies

Task dependencies will be identified and documented in the WBS. This will ensure that tasks are completed in the correct order and that the project is completed on time.

4.3 Define acceptance criteria

Acceptance criteria for each deliverable will be defined and documented. Acceptance criteria are the specific requirements that a deliverable must meet in order to be considered complete.

5. Scope Verification

5.1 Review the scope statement

The scope statement will be reviewed and approved by the project manager, sponsor, and key stakeholders. This will help to ensure that everyone involved in the project has a clear understanding of what is included (and excluded) from the project scope.

5.2 Validate deliverables

All project deliverables will be validated to ensure that they meet the acceptance criteria that were defined earlier. This will help to ensure that the project is progressing according to plan and that the final deliverables will meet the required quality standards.

6. Scope Control

6.1 Monitor and control scope changes

Any changes to the project scope will be monitored and controlled through a formal change control process. This will help to ensure that changes are properly evaluated and that their impact on the project is understood.

6.2 Update project documents

All project documents will be updated to reflect any changes to the project scope. This will help to ensure that everyone involved in the project has access to the most up-to-date information.

7. Conclusion

This Scope Management Plan outlines the process and procedures for managing the scope of the project and will be used as a reference throughout the project's lifecycle. The success of the project will depend on the ability of the project team and stakeholders to follow the procedures outlined in this document.

Have you had PMP training and presently you are filling up the PMP exam registration form? Filling the PMP exam form is not difficult. The main criteria to fill in the form is to use terminologies in the project descriptions, which you have learnt in the your PMP training.

Have a look at sample project descriptions below, and you too should write similar project descriptions in your PMP exam form.

Procedure Filling PMP Exam Application

General

PMI requires that qualified PMP candidates:

• Accomplish their responsibilities under general direction and are accountable for all project aspects

• Guide and instruct cross-functional teams to manage projects within the constraints of quality, resources, schedule, and budget

• Display adequate knowledge and skills to apply a methodology to projects that have defined project requirements and deliverables. Project descriptions should  be written to determine whether or not the documented projects are actually projects.

Furthermore, project descriptions should comprise of following:

• Brief project objective

• Deliverables of project, by process groups 
  
  
• Concise project outcome 
  
  
• Keywords (terminologies taught from PMBOK)

Real Project Descriptions (maximum 550 words)

Sample Project Description No. 1

I was involved in creation of project charter. Obtained project requirements from stakeholders. Project management plan was created which included project scope statement, WBS, plans of schedule, cost, quality, HR. I assisted to create project deliverables during project execution, monitored project management plan, including cost and schedule, ensured proper execution. Stakeholders were informed of approved changes. Project was reviewed, closed successfully, lessons learnt documented, archived documents, and project was accepted by sponsor.

Sample Project Description No. 2

Produced project scope statement, created WBS, defined activities, estimated their duration. Determined quality standards, produced quality plan, estimated cost and created project budget, identified risks, including their qualitative & quantitative analysis. Prepared risk responses. Project management plan was prepared, Directed and managed project work during project execution. Project was monitored, including cost, time, risks. Conducted project review, and project was successfully closed by acceptance. Lesson learnt were documented.

Sample Project Description No. 3

Developed project charter, collected project requirements from stakeholders, and project scope was defined. Produced project management plans, including project schedule, cost plan, HR plan, and procurement management plan. Identified quality standards, and quality management plan. Team was acquired and directed project work. Conducted procurement, and produced deliverables. Project was monitored and controlled, including control of schedule, cost, quality. Project was reviewed, accepted by user. Documents were archived. Created lessons learnt.

Sample Project Description No. 4

Identified major stakeholders and assisted in creating project charter, which included summary budget, high level project description etc. Defined project scope by producing project scope statement, created WBS, scope baseline, defined activities, and developed schedule. Assisted in developing budget. Produced project management plan, according to which executed project and produced deliverables. Monitored work, evaluated and corrected variances of cost, time etc. Project was successfully closed by acceptance. Reviewed project and created lessons leaed. Archived documents.

A Cost Management Plan according to PMBOK (Project Management Body of Knowledge) would include the following elements:

The Cost Management Plan, defined by PMBOK, includes the following sections:

1. Cost Management Plan: Outlines the general approach and policies for managing costs.
   
   
2. Budget: Provides a detailed breakdown of the project budget, categorizing costs and accounting for contingencies and reserves.
   
   
3. Cost Estimating: Explains the techniques and tools used to estimate project costs.
   
   
4. Cost Budgeting: Describes the process for creating the project budget and assigning costs to specific activities.
   
   
5. Cost Control: Covers the processes and tools for monitoring and regulating project costs, such as variance analysis.
   
   
6. Cost Forecasting: Details the process used to project future costs, including risks and assumptions.
   
   
7. Change Control: Explains the process for managing and controlling changes to the budget and their impact on costs.
   
   
8. Reporting: Outlines the cost management reporting requirements and which stakeholders need to be informed.
   
   
9. Closeout: Covers the process for concluding the project, including final cost reporting and reconciliation.

Throughout the project, the Cost Management Plan must align with the project plan and objectives and be reviewed and updated regularly as necessary.

Philosophy of EVM

What is EVM. Earned value management is a valuable technique that permits the project and program managers to effectively monitor schedule, cost, and technical project progress by the use of EVM formulas. The earned value management implementation is a highly professional function of project management. It ensures that schedule, cost, and technical features are strictly integrated. EVM has the distinctive capability to combine scope of schedule performance, cost performance, and technological operations in a sole integrated system. EVM provides an advance caution of performance issues, allowing for timely remedial measures.

Performance Forecast

All project activities should essentially earn some value, with the completion of project work. The earned value, attained by the completion of activities, is compared with the planned and actual costs to determine the performance of the project. The forthcoming trends of the performance can then be forecasted accurately. Physical progress is calculated in units of applicable currency, and then cost and schedule performance are evaluated in the similar units.

EVM Formulas, Earned Value Analysis, How to Understand?

The following are EVM formulas. For EVM formulas description, read the article Definition of EVM formulas.

SV      =    EV – PV                        + ve good

 

CV      =   EV – AC                        + ve good

SPI     =   EV/PV                          greater than 1 is good

CPI     =     EV/AC                          greater than 1 is good

EAC    = AC + BAC – EV              budgeted, atypical, no variation in future

EAC    = BAC/CCPI                      no variation in BAC, same rate spending

EAC    =     AC + (BAC-EV)/CCPI       typical, same variation in future

TCPI =     (BAC – EV)/(BAC-AC)      must meet BAC

TCP I =     (BAC – EV)/(EAC-AC)      not meet BAC, CPI decreased

VAC  =      BAC - EAC

ETC    =      EAC – AC 

% Complete =      EV/BAC

EV     =     Total months completed / Total months project  x  Total cost

PV     =     Planned % complete      x        Project budget

EV     =     Actual % complete         x        Project budget

Conclusion

Implementation of EVM in difficult and large projects include several features, indicators, and forecasts that assists to keep track of the progress with relation to the plan, and assists in timely corrective and preventive actions. However, the main function of an EVM system is its capability to measure progress by the use of EV and EV. Earned value management (EVM) measures progress objectively. Several books are available to lea more about the application of EVM formulas, and what is EVM.

Also Read:

Definition of EVM formulas.