 |
 |
 |
 |
5.1.02TS Scope Planning - Techniques
|
The following overview further describes how projects are approved, and what things need to be in place before a project begins. |
|
This supplemental content comes from the TenStep Project Management Process. |
Create Scope Management Plan - Overview (5.0.2.P1)
The Scope Management Plan is used to describe how scope will be defined, verified, and subsequently managed. The components of the Scope Management Plan include:
-
Roles and Responsibilities. You can describe who is responsible for establishing and managing project scope, who will have input into the scope definition, who can approve the scope, who can request changes to scope, who can approve scope change requests, etc.
-
Scope Definition. This section describes how you will establish the project scope. There is probably a detailed list of activities to be executed, but in this section you would summarize the high-level approach.
-
Scope Change Review and Approval Process. This section describes the organization and process for evaluating and assessing proposed scope changes. It defines the authority for accepting and approving changes to scope, which should include the customer. The evaluation process should include an assessment of the impact of proposed scope changes on the project. Impacts to cost, schedule, risk and quality should be evaluated in order to provide a basis for accepting and approving a change.
-
Tools. Describe about any scope management or scope change management tool that will be used on this project, who will have access to the tool and what various people can do with the tool.
-
Templates. It is common for there to be one or more templates in the scope definition and scope change process. The templates should be listed and described. Copies of the templates could be included at the end of the Scope Management Plan.
-
Reports. Comment here on the types and names of reports you are using to define and manage the scope, who will receive them, the frequency, etc.
-
Expected Scope Stability. This section contains a brief statement to assess the expectations regarding scope stability, i.e. whether scope is expected to change significantly during the course of the project or is expected to remain as initially defined. For example, if the scope definition is ambiguous and clarification is not possible, you can state that you expect the defined scope to be subject to many revisions, which will add more risk to the project.
[ Previous Page - 5.1 Scope Planning] [ Next Page - 5.2 Scope Definition]
