A Guide to Project Management

A Guide to Project Management

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: he scope of the project. The scope statement should include, either directly or by reference to other documents: Project justification--the business need that the project was undertaken to address. The project justification provides the basis for evaluating future tradeoffs. Project's product--a brief summary of the product description (the product description is discussed in Section 5.1.1.1). Project deliverables--a list of the summary-level subproducts whose full and satisfactory delivery marks completion of the project. For example, the major deliverables for a software development project might include the working computer code, a user manual, and an interactive tutorial. When known, exclusions should be identified, but anything not explicitly included is implicitly excluded. Project objectives--the quantifiable criteria that must be met for the project to be considered successful. Project objectives must include at least cost, schedule, and quality measures. Project objectives should have an attribute (e.g., cost), a metric (e.g., United States [U.S.] dollars), and an absolute or relative value (e.g., less than 1.5 million). Unquantified objectives (e.g., "customer satisfaction") entail high risk to successful accomplishment. .2 Supporting detail. Supporting detail for the scope statement should be documented and organized as needed to facilitate its use by other project management processes. Supporting detail should always include documentation of all identified assumptions and constraints. The amount of additional detail may vary by application area. .3 Scope management plan. This document describes how project scope will be managed and how scope changes will be integrated into the project. It should also include an assessment of the expected stability of the project scope (i.e., how likely is it to change, how frequently, and by how much). The scope management plan should also include a clear description of how scope changes will be identified and classified. (This is particularly difficult--and therefore absolutely essential--when the product characteristics are still being elaborated.) 56 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 A scope management plan may be formal or informal, highly detailed or broadly framed, based on the needs of the project. It is a subsidiary component of the project plan (described in Section 4.1.3.1). 5.3 SCOPE DEFINITION Scope definition involves subdividing the major project deliverables (as identified in the scope statement as defined in Section 5.2.3.1) into smaller, more manageable components to: Improve the accuracy of cost, duration, and resource estimates. Define a baseline for performance measurement and control. Facilitate clear responsibility assignments. Proper scope defini...
View Full Document

This document was uploaded on 09/27/2013.

Ask a homework question - tutors are online