Scope Management-PMBOK 4th Edition

Discussion Topics

Abhinav(Abhi)

Collect Requirements : Describe how to define, verify and control scope and how to create WBS.
Define Scope : Create scope statement; this will guide future decisions. Describes deliverables and work required to create them.
Create WBS: Deliverable oriented hierarchy that breaks down the work to be done.
Verify Scope : Validating and approving project deliverables against the baseline and gaining acceptance from the customer.
Control Scope l: Controlling changes related to scope. Approved scope must be exactly what is implemented; no more, no less.

# Product scope is requirements that relate to the production of a product; project scope is the work required to complete the project.

WBS is broken down from the top. The lowest level in the WBS is a work package, but even this is broken down further into schedule activities during activity definition. Work packages are charged to control accounts for cost management. The word task is not used in the PMI vocabulary; think "work package" and "schedule activity" instead.
The WBS is just numbers and titles; the WBS dictionary provides the textual explanations required (statement of work, defined deliverables, responsible individuals, milestones, etc.)
WBS is the most important element in project management planning. It should exist for every project.
WBS identifies all work to be performed; if it's not in the WBS, it shouldn't be in the project. Beware of scope creep and gold-plating!
WBS is a tool to assist the project manager in decomposition.
WBS does not show dependencies the way a network diagram does

Edited: January 20, 2010 01:30AM