Ch. 5: Managing the Project Scope Flashcards
A planning heuristic for creating the WBS. This rule states the work package in a WBS must take no more than 80 hours of labor to create and no less than eight hours of labor to create.
8/80 Rule
A scope definition process of finding alternative solutions for the project customer while considering the customer’s satisfaction, the cost of the solution, and how the customer may use the product in operations.
Alternative identification
Documented in the scope management plan, this system defines how changes to the project scope may be allowed.
Change control system
A hierarchical numbering system for each item in the WBS. The PMBOK is a good example of a code of accounts, as each chapter and its subheadings follow a logical numbering scheme. For example, PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOK.
Code of accounts
This is the study of the functions within a system, project, or, what’s more likely in the project scope statement, the product the project will be creating. Functional analysis studies the goals of the product, how the product will be used, and the expectations the customer has of the product once it leaves the project and moves into operations. Functional analysis may also consider the cost of the product in operations, which is known as life cycle costing.
Functional analysis
Most projects have a determined budget in relation to the project scope. There may be a qualifier on this budget, such as plus or minus 10 percent based on the type of cost estimate created.
Fund limitation
The project scope statement identifies the project team and the key stakeholders. In some organizations, especially on larger projects, the team organization and structure is also documented.
Initial project organization
This project scope statement component works with the project requirements, but focuses specifically on the product and what the conditions and processes are for formal acceptance of the product.
Product acceptance criteria
A scope definition technique that breaks down a product into a hierarchical structure, much like a WBS breaks down a project scope.
Product breakdown
Defines the product or service that will come about as a result of completing the project.
Product scope
This is a narrative on what the project is creating as a deliverable for the project customer.
Product scope description
A project assumption is anything that is held to be true but not proven to be true.
Project assumptions
A project boundary clearly states what is included with the project and what’s excluded from the project. This helps to eliminate assumptions between the project management team and the project customer.
Project boundaries
A constraint is anything that limits the project manager’s options. Consider a predetermined budget, deadline, resources, or materials the project manager must use within the project—these are all examples of project constraints.
Project constraints
These are the measurable goals that determine a project’s acceptability by the project customer and the overall success of the project. Objectives often include the cost, schedule, technical requirements, and quality demands.
Project objectives