Model Guideline #10
Show me a typical
guideline for -
Work Breakdown
Structure & Scope of Work
Guideline Goal
To establish an
effective and consistent methodology for identifying, communication and
controlling all elements of a project as set out in the complete Systems
Scope Description
Expectations - 1
-
Early in Phase 2 of the project, the entire set of systems required
for the project will be identified
-
And the technical performance of each established
-
Each system will be documented in a Systems Scope Description
Expectations - 2
-
To the extent possible or reasonable, a hierarchical Work Breakdown
Structure (WBS) will be developed for every project
-
Consisting of a set of discrete Work Packages
-
Reflecting the project's complete Systems Scope Description
Expectations - 3
-
From the WBS will be derived a Scope of Work statement
-
Describing all the work to be performed on the project
-
As a basis for developing Project Implementation Plans, Project
Schedules, & Project Estimates
Expectations - 4
-
This documentation will be used as the common frame of reference
throughout the remainder of the Project for updating
-
The Implementation Plans
-
Project Schedules
-
Forecasts-to-complete and
-
Project Progress Reports
Particulars
-
The Work Breakdown Structure, and its resulting Work Packages, is a
powerful tool for organizing and communicating
-
Project Requirements
-
Expectations, and
-
Details of the work to be done
-
The final version of the WBS must be consistent with the Project
Implementation Plan
Definitions and Responsibility
Definitions to be
included
-
Scope of Work, System Scope Description Work Breakdown
Structure, Work Package
Primary responsibility
Responsible to