| Project Scope of Work: | | | | organizations such as project users, system owner, |
| POME recommends a documented procedure for | | | | procurement, human resources, finance, enterprise |
| conducting its project scope management activities. | | | | architecture and others as appropriate. |
| Typical items in the procedure include— | | | | RECORD OF AMENDMENTS |
| - Assigning responsibilities for project scope | | | | |
| management | | | | Version |
| - Developing a scope management plan for every | | | | Author |
| project as a separate document or as part of other | | | | Date |
| planning documents | | | | Comments |
| - Defining project scope by subdividing the major | | | | |
| project deliverables into smaller, more manageable | | | | |
| components | | | | 1.0 |
| - Formalizing the acceptance of project scope by | | | | |
| project members through a scope verification process | | | | 07/25/09 |
| - Establishing a scope change control system | | | | Draft 1 – Based on template created for scope |
| - Ensuring that scope verification is performed | | | | statements |
| - Documenting lessons learned | | | | |
| - Establishing and using project templates | | | | |
| - Integrating product scope and project scope so that | | | | |
| the work of the project results in delivery of the | | | | |
| specified product or service | | | | Scope Management Plan Illusration Template |
| | | | | |
| Items typically addressed in integrating product scope | | | | The following are suggested sections for the Scope |
| and project scope include— | | | | Management Plan |
| - Features and functions to be included in a product or | | | | Purpose of Scope Management Plan |
| service (product scope) | | | | Describe the purpose of the Scope Management Plan |
| - Work that must be done to deliver a product scope | | | | using the following guidelines. Do not merely describe |
| with the specified features and functions (project | | | | the content of the plan, but explain why Scope |
| scope) | | | | Management is necessary for the project. |
| - Description of the processes, tools, and techniques | | | | Scope changes are common in projects, especially |
| used to manage both product scope and project | | | | complex projects, as more information and detail |
| scope are the following:- | | | | become available during project planning and |
| - Objectives | | | | execution. Some changes are necessities in that the |
| - Commitment to perform | | | | end product may not meet the project objectives if |
| Description of the methods to measure completion of | | | | the changes are not incorporated. Some changes |
| both product scope and project scope | | | | are "nice to have" features that really are not essential |
| Importance of integrating product scope and project | | | | to meeting the project end product objectives but |
| scope | | | | would enhance the product. Some changes are |
| Description of the methods to integrate any scope | | | | simply included due to a difference in approach, style |
| changes into the project | | | | or priority but are not essential at all to meeting project |
| | | | | objectives. |
| The project manager and the other parties will review | | | | |
| and agree on all customer commitments. The purpose | | | | A management process must to be established that |
| of this review is to— | | | | will allow the evaluation and impact assessment of |
| - Support formal acceptance of the product or service | | | | proposed scope changes. Any change in scope will |
| of the project | | | | have some impact on cost, time or quality of the |
| - Adequate resources are provided for project | | | | project's end product. Before decisions can be made |
| - Scope management activities. | | | | regarding the proposed change the impact of that |
| - Experienced individuals, who have expertise in | | | | change must be known. Therefore a scope |
| requirements definition, WBS development, change | | | | management process must be a part of the Project |
| control, and scope verification, are made available to | | | | Plan. The objective of the scope management plan |
| support project scope management activities. | | | | is to make sure the scope is delivered – no more |
| - Ensure that all products or services are completed | | | | and no less. |
| as specified and meet the customer's expectations | | | | The scope of a project should be captured in the |
| | | | | Work Breakdown Structure (WBS). The WBS |
| Tools and techniques to support project scope | | | | organizes the project by major functions (project |
| management activities are made available. Examples | | | | planning, standards documentation, training etc.), |
| of tools and techniques include— | | | | continuous processes (status reporting, financial |
| - Relevant Templates | | | | reporting, etc.), and primary deliverables. The WBS |
| - Project management software | | | | is the primary tool for managing the scope of the |
| - Adequate time is allocated for project scope | | | | project. This simply means that if the work is included |
| management activities. | | | | within the WBS, it is considered within scope. If work |
| - Funding is made available for project scope | | | | is not contained within the WBS, it is considered "out of |
| management activities. | | | | scope" and should not be included in the project's end |
| - Support is made available for implementing | | | | product. The Work Breakdown Structure is the |
| improvements in project scope engagement. | | | | fundamental planning tool for project management. |
| | | | | Roles and Responsibilities |
| Scope change control training is provided to | | | | Describe how the following project participants, at a |
| appropriate project implementation team and | | | | minimum, perform in the planning and execution of |
| members. Topics in this training typically include— | | | | project communications |
| - Developing a scope change request | | | | ▲ Project Sponsor |
| - Determining factors that create scope changes | | | | ▲ Project Manager |
| - Determining whether a change has occurred | | | | ▲ Project Team |
| - Managing scope changes | | | | ▲ Project Stakeholders |
| - Tracking the resolution of scope change requests | | | | |
| - Authorizing scope changes | | | | Work Breakdown Structure (WBS) Development |
| | | | | The plan should discuss the process the project will |
| ABILITY TO PERFORM: an orientation on scope | | | | follow to develop the WBS (an outline or graphical |
| verification is provided to directors and project | | | | depiction of the project scope). The development |
| members. Typical areas covered in such an orientation | | | | process involves deciding on an approach (usually |
| include— | | | | top-down), involving team members who will |
| - Definition of scope verification | | | | accomplish the work (tasking them for inputs, |
| - Reviewing requirements of deliverables | | | | meetings), creating a numbering system, including |
| - Inspection activities as tools and techniques for scope | | | | financial system codes and budgetary information, and |
| verification | | | | deciding where to capture costs (work package level). |
| - Formal customer acceptance documentation | | | | A thorough understanding and buy-in of the WBS from |
| requirements | | | | the project team and supporting organizations is |
| | | | | essential. |
| Activities performed | | | | Scope Baselining |
| The scope statement is reviewed and validated with | | | | Describe the process for establishing the scope |
| the customer before it is finalised. The purpose of this | | | | baseline (essentially freezing WBS development). The |
| review is to ensure the following— | | | | formal process to insure the project team and |
| - Customer requirements are reflected accurately in | | | | stakeholders understand the WBS and are supportive |
| the project objectives | | | | of its layout. The baselined WBS can then become the |
| - Project objectives are measurable | | | | backbone for establishing a detailed project schedule |
| - Project deliverables conform to customer | | | | and cost accounting system. The integrated change |
| expectations | | | | control process must be followed to initiate further |
| A documented scope management plan is developed | | | | changes or revision to the WBS (schedule, budget, risk |
| and used by the project team as the basis for | | | | database, requirements, acquisition plan, etc.) if |
| performing the project scope management activities; | | | | rebaselining occurs. Discuss the possible use of a |
| this plan may be a standalone document or part of the | | | | Change Control Board (CCB). |
| overall project plan. The project scope management | | | | Scope Change Management Process |
| plan typically describes the— | | | | Describe the scope (WBS) change control process as |
| - Management of project scope | | | | it pertains to project integrated change control. Discuss |
| - Integration of scope changes into the project | | | | the likelihood that WBS changes will be necessary. As |
| - Expected stability of the project scope | | | | an example, progressive elaboration of the project |
| - Identification, classification, and assessment of scope | | | | product can lead to changes to the WBS. Discuss the |
| changes | | | | frequency of anticipated changes. Describe how |
| - Submission, review, and decisions concerning scope | | | | scope changes will be identified classified and |
| change requests | | | | assessed (major cost and schedule impact, minor |
| | | | | impact, no impact, etc). Do scope changes require |
| Scope Statement Illustration Project Format: | | | | changes to the scope statement, WBS, or schedule? |
| Purpose of Scope Statement | | | | Include a process for tracking scope changes, |
| Describe the purpose of the scope statement using | | | | continuously evaluating the overall impact of changes, |
| the following guidelines: | | | | and reporting changes to sponsors, senior |
| The Scope Statement is distributed to all the project | | | | management, stakeholders, project team members |
| stakeholders for their approval. It documents a | | | | (immediately, at status reviews, etc.). Discuss the |
| description of the project, including the objectives, | | | | triggers for rebaselining the WBS and process for |
| planned deliverables, and requirements. It becomes | | | | revising project documents (schedule, budget, risk |
| the baseline document that can only be changed | | | | database, requirements, acquisition plan, etc.) if |
| through the process outlined in the Scope | | | | rebaselining occurs. Discuss the possible use of a |
| Management Plan. | | | | Change Control Board (CCB).The integrated change |
| The Scope Statement documents a description of the | | | | management process must be followed to initiate any |
| project, including the objectives, planned deliverables, | | | | changes or revisions to the WBS. Scope changes |
| and requirements. It becomes the baseline document | | | | can be impacted by any aspect of the project, |
| that can only be changed through the process outlined | | | | including schedule, budget, risks, requirements, |
| in the Scope Management Plan. | | | | acquisition plan etc. The integrated change |
| Project Business Need | | | | management plan is described in the document titled |
| Provide the justification in terms of the problems the | | | | EVM Change Management.doc. |
| project will address and/or the improvements it will | | | | Change Thresholds |
| implement. The business need impacts the ability to | | | | Submittal of a change request to the [sponsor] for |
| assess project alternatives. | | | | approval is required if one of the two following |
| Project History | | | | statements is true: |
| Provide a short narrative of the events that lead up to | | | | 1. The change is estimated to reduce the cost or |
| project approval. This helps to put the project | | | | duration of an individual activity by x% or more, or |
| description into context and supports the rest of the | | | | increase the cost or duration of an individual activity by |
| document. | | | | x% or more |
| Project Description/ Objectives | | | | 2. The change is estimated to reduce the cost or |
| Describe the project in terms of strategy, timing, | | | | duration of the overall schedule by x% or more, or |
| objectives and deliverables. | | | | increase the cost or duration of the overall schedule |
| Project Product Requirements | | | | by x% or more |
| Provide a description of the project's product or | | | | Change requests that do not meet these threshold |
| service, its use, technical parameters, requirements, etc. | | | | levels are to be submitted to the [Project Manager] for |
| Project Deliverables | | | | approval. |
| Provide the stakeholders a list of the project | | | | Approved scope changes may or may not require |
| deliverables. | | | | re-baselining. In other words, a change in scope may |
| Project Assumptions and Constraints | | | | not necessarily change the schedule or cost and |
| Assumptions describe details that are considered to | | | | therefore would not require re-baselining. In |
| be true or certain that impact the success of the | | | | determining whether to make a scope change, |
| project. Examples would be available critical | | | | consideration will be given to impacts on schedule, cost, |
| personnel or funding. Constraints describe factors the | | | | risk, quality and staffing. The integrated change |
| impact the project such as: budget limitations, | | | | management plan contains further explanation of the |
| organizational policies, statutes or regulations. | | | | re-baselining process. The status of all change |
| Assumptions | | | | requests is communicated to appropriate project |
| ▲ | | | | stakeholders in accordance with the project's |
| Constraints | | | | communications plan. |
| ▲ | | | | All change requests are documented using a change |
| Quality Assurance Manager Activities | | | | request form. The change request form is included in |
| Generally describe the activities of the QA manager | | | | the integrated change management plan document |
| as they relate to specific deliverables. What will the | | | | along with instructions on how to complete it. |
| QA manager do to supplement the testing and | | | | The project Scope Statement must be reviewed for |
| acceptance process? | | | | any impacts as part of a change request submission. |
| Signature Page | | | | Any scope changes also affecting the scope |
| The Scope Statement is distributed to all the project | | | | statement must be noted on the request form. The |
| stakeholders for their approval. Signature blocks | | | | change request is then processed through the |
| should be provided for the project sponsor, the project | | | | approval process with knowledge that the scope |
| manager and the primary resource managers from | | | | statement also requires revision. |