Chapter 5 - Project Scope Management 9% Flashcards
A decision that is reached whereby everyone agrees on a single course of action.
Unanimity
A decision that is reached whereby the largest block in a group decides, even if a majority is not achieved, this method is generally used when a number of options nominated is more than two.
Plurality
A document that provides detailed deliverable, activity, and scheduling information about each component in the WBS.
WBS Dictionary
A facilitation technique that helps determine critical characters for new product development in the manufacturing industry. It starts by collecting customer needs, AKA the voice of the customer (VOC). These needs are then objectively sorted and prioritized and goals are set for achieving them.
Quality Function Deployment (QFD)
A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.
Work Breakdown Structure (WBS)
A set of conditions that are required to be met before deliverables are accepted.
Acceptance Criteria
A technique that uses a decision matrix to provide a systematic analytical approach for establishing criteria, such as risk levels, uncertainty, and valuation, to evaluate and rank many ideas.
Multicriteria Decision Analysis
A technique used for dividing and subdividing the project scope and project deliverables into smaller, more manageable parts.
Decomposition
A WBS component below the control account and above the work package with known work content but without detailed schedule activities.
Planning Package
An example of a scope model that visually depicts the product scope by showing a business system (process, equipment, computer system, etc.) and how people and other systems (actors) interact with it.
Context Diagram
Describes the behaviors of the product. Examples includeactions, processes, data, and interactions that the product should execute.
Functional Requirements
Examines project performance over time to determine if performance is improving or deteriorating.
Trend Analysis
Identifies what is excluded from a project. Explicitly stating what is out of scope for the project helps manage stakeholders’ expectations and can reduce scope creep.
Project Exclusions
Includes activities such as measuring, examining, and validating to determine whether work and deliverables meet requirements and product acceptance criteria. Sometimes called reviews, product reviews, and walkthroughs, but sometimes those terms mean very diff things.
Inspection
One individual takes responsibility for making the decision for the group.
Autocratic Decision Making
Progressively elaborates the characteristics of the product, service, or result described in the project charter and requirements documentation.
Product Scope Description
Short, textual descriptions of required functionality that are often developed during a requirements workshop. These describe the stakeholder role, who benefits from the feature (role), what the stakeholder needs to accomplish (goal), and the benefit to the stakeholder (motivation).
User Stories
Supplement other solution requirements and describe the environment conditions or qualities required for the product to be effective - reliability, security, performance, safety, level of service, supportability, retention/purge, etc.
Nonfunctional Requirements
The description of the project scope, major deliverables, and exclusions that documents the entire scope, including project and product scope.
Project Scope Statement
Defined whether waterfall, iterative, adaptive, agile, or a hybrid ______ will be used.
Development approach