- Define scope and describe how it is affected by project complexity.
- Identify the uses of a scope document.
- Describe how a scope document is developed and changed.
The project scope identifies the total work of the project.
Definition of Scope and the Effects of Complexity
The scope document defines what tasks the project team is expected to accomplish and, just as importantly, what is not part of the project. Depending on the complexity level of the project, the scope document can be as short as one page or as long as several hundred pages. On more technical projects, such as a project to design an offshore wind-turbine farm, the scope would include a significant amount of technical specifications, with a focus on the electrical output from the wind turbines. The size and character of the project scope document is related to the project complexity. Higher scores on the Darnall-Preston Complexity Index indicate the need for more detailed scope documents.
Uses of a Scope Document
A well-developed project scope statement provides the project team with information the team needs to design and implement the project execution plan. The well-developed project scope also provides the team with an understanding of the purpose of the project and the basis for defining project success.
Scope Document for Training Auto Workers
An automotive company is building a new plant to produce electric passenger cars in the southeast United States. As the plant nears completion, the plant’s manager issues a contract to train the new plant workers. The training of workers who will be maintaining the production equipment will be done by the equipment suppliers and will not be in the scope of the training contract.
The automotive project described above is a typical example of the types of information and the people involved in developing a project scope. From the information in the project description, the project team could develop a project scope document.
Development of a Scope Document
The project manager will often develop the first draft of the project scope and then solicit feedback and suggestions from the project team, client, and sometimes key vendors. The project manager will attempt to develop consensus around the project scope, but the final approval belongs to the project client or sponsor. Depending on the complexity profile of the project, the development of the project scope document can be a short discussion between the project manager and the client, or on a large, complex project, the process can take weeks.
Managing Changes to the Scope Document
The project scope is not a stagnant document, and changes are to be expected. Changes to the project scope are necessary to reflect new information. Changes to the project scope also create the opportunity for new purposes to emerge that will change the end results of the project. In some cases, these new results represent a positive outcome for the chartering organization.
Deviation versus Change
If a minor change is made to the schedule that does not affect the completion date of the project, it is a deviation from the schedule. As long as the end date of the project or major objectives are not delayed, a formal change request to the client is not needed. Recording and communicating these schedule deviations is still important for coordinating resources and maintaining the client’s awareness of the project’s progress.
Deviation of Labor Cost
The labor cost was estimated at fifteen dollars per hour for cleaning the project office once per week. The winning bid for the contract was at sixteen dollars per hour. The cost deviated from the estimate and a change was made to the budget. This was a cost deviation, not a change in scope. The additional cost for the contract was covered from the project contingency reserves, and the budget was revised to reflect the changes.
Truck Crash Causes a Deviation to the Schedule
Installation of a fence around the project site was delayed when the truck delivering the fence was wrecked on the way to the job site. The fence project was delayed by one week and the delay did not affect any other activity on the project. This deviation from the original schedule did not cause a delay in the project, and the schedule was adjusted as a deviation to the schedule—not a change request.
It is important to have a written record of changes to the scope of a project. On the least complex projects, an e-mail message can be sufficient, but on larger projects a standard form is normally used. The following steps are paraphrased by Tom Mochal (Mochal & Mochal, 2003), and they have the necessary components of a change documentation process:
- Inform project stakeholders of the change request process.
- Require that the change request is made in writing, including the business value of the change to the project.
- Enter the request in the scope change log.
- Estimate the time needed to evaluate the change. If the evaluation process is time consuming and would affect activity completion dates by diverting management resources, get approval from the project sponsor to evaluate the change request. If the evaluation is not approved, record the decision in the scope change log.
- Evaluate the change and its impact on the schedule and budget if the evaluation is approved.
- Present the change request to the project sponsor for approval. Record the decision in the scope change log with the recommended course of action.
- Distribute the scope change log periodically to team members so they know what changes are being considered and what happened to those that were not approved or evaluated.
- If the change is approved, update the project charter or other initiation documents.
- Update the work plan.
- Distribute the revised work plan to stakeholders and team members.
- Scope is a description of the major tasks that are included in the project and some of the tasks that are specifically not included. More complex projects require more detailed and specific scope documents.
- A scope document is used to provide the project team with the information it needs to design and implement the project plan. It provides understanding of the purpose of the project and what project success would be.
- The scope document begins as a draft that is circulated for comments by the team, client, and in some cases, key vendors. The final draft is approved by the client or sponsor. Changes to the scope are documented carefully using standard forms and processes and approved by the project sponsor or client.
- How is the scope statement affected by the complexity of the project?
- What negative aspect of the scope statement is important?
- What are the uses of a scope statement?
- Once a scope statement is agreed to, how is it changed and what is always required when a scope statement is changed?
Internalize your learning experience by preparing to discuss the following.
Mochal, T. and Jeff Mochal, Lessons in Project Management (Berkeley, CA: Apress, 2003).