A Guide to Project Management

By contractual provisions are often important

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: tion, and this other organization 60 NAVIGATION LINKS ACROYMNS LIST ACRONYMS LIST ACROYMNS LIST A Guide to the Project Management Body of Knowledge (PMBOK Guide) 2000 Edition 2000 Project Management Institute, Four Campus Boulevard, Newtown Square, PA 19073-3299 USA Chapter 5--Project Scope Management must plan and manage the scope of work at a more detailed level than the project manager in the main project. These work packages may be further decomposed in the project plan and schedule, as described in Sections and Work component descriptions are often collected in a WBS dictionary. A WBS dictionary will typically include work package descriptions, as well as other planning information such as schedule dates, cost budgets, and staff assignments. The WBS should not be confused with other kinds of "breakdown" structures used to present project information. Other structures commonly used in some application areas include: Contractual WBS (CWBS), which is used to define the level of reporting that the seller will provide the buyer. The CWBS generally includes less detail than the WBS used by the seller to manage the seller's work. Organizational breakdown structure (OBS), which is used to show which work components have been assigned to which organizational units. Resource breakdown structure (RBS), which is a variation of the OBS and is typically used when work components are assigned to individuals. Bill of materials (BOM), which presents a hierarchical view of the physical assemblies, subassemblies, and components needed to fabricate a manufactured product. Project breakdown structure (PBS), which is fundamentally the same as a properly done WBS. The term PBS is widely used in application areas where the term WBS is incorrectly used to refer to a BOM. .2 Scope statement updates. Include any modification of the contents of the scope statement (described in Section Appropriate stakeholders must be notified as needed. A Guide to the A Guide to the Project Project Management Management Body of Body of KnowledgeE L KnowledgeE PL 5.4 SCOPE VERIFICATION Scope verification is the process of obtaining formal acceptance of the project scope by the stakeholders (sponsor, client, customer, etc.). It requires reviewing deliverables and work results to ensure that all were completed correctly and satisfactorily. If the project is terminated early, the scope verification process should establish and document the level and extent of completion. Scope verification differs from quality control (described in Section 8.3) in that it is primarily concerned with acceptance of the work results while quality control is primarily concerned with the correctness of the work results. These processes are generally performed in parallel to ensure both correctness and acceptance. Inputs .1 .2 .3 .4 .5 Work results Product documentation Work breakdown structure Scope statement Project plan MP AM SA S Tools & Techniques .1 Inspection Outputs .1...
View Full Document

{[ snackBarMessage ]}

Ask a homework question - tutors are online