Scope Management

	Scope Management

Sections

[Project Management Home]

[Reference Material to Study] [What to Study?] [Key Definitions] [Scope Management Processes] [Scope Management Concepts] [Sample Questions] [Answers]

[Other Knowledge Areas]

The project scope management knowledge area is defined by the processes that limit and control the work included in a project. These processes ensure that all the work of the project is included. Processes in this knowledge area include the initiation process as well as all the processes related to the scoping of the project. Each process has a set of input and a set of output. Each process also has a set of tools and techniques used to convert input into output.

Reference Material to Study

	- A Guide to the Project Management Body of Knowledge, Chapter 5 (1996 & 2000 edition) - PMBOK (1996) Q&A, PMI, Scope Section

	Project Planning, Scheduling & Control, Lewis, James P., 1995 Chapters 4.

	Effective Project Management, Chapter 6. Wysocki / Beck Jr. / Crane.

	The New Project Management, Chapters 8, 12-13, Frame, J. Davidson, 1994

	Earned Value Project Management, Second Edition, Chapter 5. Flemming and Koppleman

	Project Management: A Managerial Approach, pp. 43-44. Meredith and Mantel

	ESI PMP Challenge!, Scope Section, Ward, J. Leroy, Oct. 1996

What to Study?

The PMBOK framework (first 3 chapters): Introduction, The Project Management Context; and Project Management Processes
Chapter 5 of the PMBOK on the Project Scope Management processes: Initiation, Scope Planning, Scope Definition, Scope Verification, and Scope Change Control.
(Be familiar with Input, Tools and Techniques, and Output for each phase)
Know the difference between project and product scope.
Know the difference between a scope statement and a statement of work (SOW).
Know key definitions (see list in study notes or PMBOK glossary).
Know the phases of a generic life cycle. Also know what is generally done in each phase.
Know what is entailed in each of the phases of a generic life cycle.
Know what a Work Breakdown Structure (WBS) is and what it is used for.
Know what a work package is and how it relates to the WBS.
Know how to label the levels of a WBS chart.
Know what a project plan is and how it is used.

Key Definitions

Scope

The sum of the products and services to be provided in a project.

Product Scope

The features and functions that are to be included in a product or service.

Project Scope

The work that must be done in order to deliver a product with the specified i features and functions.

Scope Change

Any change to the project scope.

Scope Change Control

Controlling changes to project scope.

Scope Definition

Decomposing the major deliverables into smaller, more manageable components to provide better control.

Scope Planning

Developing a written scope statement that includes the project justification, the major deliverables, and the project objectives.

Scope Management

A plan which describes how project scope will be managed and how

Plan

Scope change will be integrated into the project. Includes an assessment of how likely and frequently the project scope may change and a description of how scope changes will be identified and classified.

Scope Statement

A documented description of the project as to its output, approach, and content. (What is being produced?, How is it being produced?, and What is included?)

Work Breakdown Structure (WBS)

A deliverable-oriented grouping of project elements which organizes and defines the total scope of the project.

Work Package

A deliverable at the lowest level of the work breakdown structure. A work package may be divided into activities.

Scope Management Processes

Initiation

Process Group: Initiating
Input includes: product description; strategic plan; project selection criteria; historical information

Methods used: project selection methods and expert judgment from other units within the organization; consultants; industry groups; or professional / technical associations.

Output includes: scope statement; supporting detail, scope management plan, project charter, identified project manager, constraints, and assumptions.

Committing the organization to begin the next phase of the project.

The process of formally recognizing that a new project exists or that an existing project should continue to its next phase.

Scope Planning

Process Group: Planning

Input includes: the product description; project charter; constraints, and assumptions.

Methods used: product analysis; benefit / cost analysis; identifying alternatives, and expert judgment.

Output includes: scope statement; supporting detail, and scope management plan

The process of developing a written scope statement as the basis for future project decisions.

The scope statement forms the basis for an agreement between the project team and the project customer by identifying the project objectives and major project deliverables.

Scope Definition

Process Group: Planning

Input includes: scope statement; constraints; assumptions; and historical information.

Methods used: work breakdown structure templates (or WBS from a previous project) and decomposition (subdivision).

Output includes: work breakdown structure

The process of subdividing the major project deliverables into smaller, more manageable components.

Scope Verification

Process Group: Controlling

Input includes: work results (completed or partially completed deliverables, incurred or committed costs, etc.), and product documentation (plans, specifications, technical documentation, etc.)

Methods used: inspection (measuring, examining, reviewing and testing to determine if results conform to requirements)

Output includes: formal acceptance

The process of formally accepting the project scope by the stakeholders (sponsor, client, customer, etc.)

Scope Change Control

Process Group: Controlling

Input includes: WBS, performance reports, change requests, and the scope management plan.

Methods used: a scope change control system; performance measurement techniques; and additional planning.

Output includes: scope changes; corrective action, and lessons learned.

The process of controlling changes to project scope.

Scope Management Concepts

Work Breakdown Structure

An output of the scope definition process. Used as input into the scope change control process.

Developing a WBS (from Infotech notes):

Identify major issues.
Break down each issue into smaller deliverable units.
Subdivide deliverables into measurable units.
Define each work package as sub-contractable units of work.
Review for patterns and anomalies.
review again.

Developing a WBS (from Project Planning, Scheduling & Control by Lewis):

What tasks must be done?
Who will do each one?
How long will each task take?
What materials / supplies are required?
How much will each task cost?

Examples of names of WBS structure levels:

Program
Project
Task
Sub-Task
Work Package

See PMBOK'1996 pgs. 54-55 for examples of WBS's.

Work Package

The lowest level of a WBS.

Work packages are further broken down during the Activity Definition Process. (part of Time Management)

Scope Management Plan

A subsidiary element of the overall project plan.

Describes how project scope will be managed.

Describes how scope changes will be integrated into the project.

Should also include an assessment of the expected stability of the project scope.

Should also include a clear description of how scope changes will be identified and classified.

Sample Questions

Get All Questions

There are 47 questions related to project scope management. Simply click the 'All Questions' link in order to go to them.

[All Questions]

Go to Specific Question

Following is a list of the questions and the general subject of the question. Click the number in order to go directly to that question.

[1] WBS
[2] Scope Management Processes
[3] Terminology
[4] WBS
[5] WBS
[6] Change Requests
[7] Terminology
[8] Scope Management Processes
[9] Scope Management Processes
[10] Scope Management Processes
[11] Documentation
[12] Terminology
[13] Scope Management Processes
[14] Scope Management Processes
[15] Scope Management Processes
[16] Terminology
[17] Terminology
[18] Tools and Techniques
[19] WBS
[20] Terminology
[21] Terminology
[22] WBS
[23] WBS
[24] Terminology
[25] Terminology
[26] Terminology
[27] WBS
[28] Terminology
[29] WBS
[30] Terminology
[31] Terminology
[32] Tools and Techniques
[33] Tools and Techniques
[34] Terminology
[35] Scope Management Processes
[36] Tools and Techniques
[37] Tools and Techniques
[38] WBS
[39] Tools and Techniques
[40] Terminology
[41] Tools and Techniques
[42] WBS
[43] WBS
[44] Tools and Techniques
[45] Tools ad Techniques
[46] Tools and Techniques
[47] Tools and Techniques

Answers

Get All Answers

[All Answers]

Go to Specific Answer

[1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24] [25] [26] [27] [28] [29] [30] [31] [32] [33] [34] [35] [36] [37] [38] [39] [40] [41] [42] [43] [44] [45] [46] [47]

Other Knowledge Areas
[Integration] [Scope] [Time] [Cost] [Quality] [Human Resources] [Communications] [Risk] [Procurement]