5.2 Scope Planning

Introduction

Scope planning is the process of developing a written scope statement as the basis for future project decisions including, in particular, the criteria used to determine if the project or phase has been completed successfully.

It forms the basis for an agreement between the project team and the project customer by identifying both project objectives and major project deliverables.

5.2.1 Inputs

5.2.2 Tools & Techniques

Product analysis
Benefit/cost analysis
Alternatives identification
Expert judgement

5.2.3 Outputs

Scope statement
Supporting detail
Scope management plan

5.2.2 Scope Planning - Tools and Techniques

5.2.2.1 Product analysis

It involves developing a better understanding of the product of the project by using:

systems engineering
value engineering
value analysis
function analysis
quality function deployment

5.2.2.2 Benefit/cost analysis

This involves estimating tangible and intangible costs and benefits of various project alternatives and then using financial measures such as ROI or payback to assess their relative desirability.

5.2.2.3 Alternatives identification

Other techniques eg brainstorming and lateral thinking.

5.2.2.4 Expert judgement

Also used in Initiation.

Return to Top of Page

5.2.3 Scope Planning - Outputs

5.2.3.1 Scope statement

The scope statement provides a documented basis for making future project decisions and for confirming or developing common understanding of project scope among stakeholders. This should include

Project justification - the business need that the project was undertaken to address
Project product - a brief summary of the product description
Project deliverables - a list of summary level sub-products whose full and satisfactory delivery marks the completion of the project
Project objectives - the quantifiable criteria that must be met for the project to be successful - they must include at least cost, schedule and quality measures and have an attribute, a yardstick and an absolute or relative value. Unquantified objectives (eg customer satisfaction) entail high risk.

5.2.3.2 Supporting Detail

Supporting detail for the scope statement should always include documentation of all identified assumptions and constraints. This maye be used to facilitate other project management processes.

5.2.3.3 Scope management plan

This describes how project scope will be managed and integrated. It should include:

an assessment of expected scope stability - how likely is it change
a clear description of how scope changes will be identified and classified

The scope management plan may be formal or informal, detailed or broadly framed based on needs of the project. It is a subsidiary element of the overall project plan.

Return to Top of Page