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
The features and functions that characterize a product, service, or result.
Product Scope
The lowest level of the WBS and has a unique identifier. These identifiers provide a structure for hierarchical summation of costs, schedule, and resource information and form a code of account.
Work Package
The process for formalizing acceptance of the completed project deliverables.
Validate Scope
The process of creating a scope management plan that documents how the project and product scope will be defined, validated, and controlled.
Plan Scope Management
The process of determining, documenting, and managing stakeholder needs and requirements to meet objectives.
Collect Requirements
The process of developing a detailed description of the project and product.
Define Scope
The process of formalizing acceptance of the completed project deliverables.
Validate Scope
The process of monitoring the status of the project and product scope and managing changes to the scope baseline.
Control Scope
The process of subdividing project deliverables and project work into smaller, more manageable components.
Create WBS
The description of this determines the series of phases that a project passes through from its inception to the end of the project.
Project Life Cycle Description
The work performed to deliver a product, service, or result with the specified features and functions. The term is sometimes viewed as including product scope.
Project Scope
The ______ has information on how project requirements will be collected, analyzed, and documented.
Requirements Management Plan
The ______ is a component of that project or program management plan that describes how the scope will be defined, developed, monitored, controlled, and validated.The development of the ______ and the detailing of the project scope begin with the analysis of information contained in the project charter, the latest approved subsidiary plans of the project management plan, historical information contained in the organizational process assets, and any other relevant enterprise environmental factors.
Scope Management Plan
The ______ is a grid that links product requirements from their origin to the deliverables that satisfy them.
Requirements Traceability Matrix
The ______ is used to understand stakeholder communication requirements and the level of stakeholder engagement in order to assess and adapt to the level of stakeholder participation in requirements activities.
Stakeholder Engagement Plan
These capture any condition or criteria needed to validate the successful completion of a project deliverable or fulfillment of other project requirements - tests, certifications, validations, etc.
Quality Requirements
These describe features, functions, and characteristics of the product, service, or result that will meet the business and stakeholder requirements. These are further grouped into functional and nonfunctional requirements.
Solution Requirements
These describe temporary capabilities, such as data conversion and training requirements, needed to transition from the current as-is state to the desired future state.
Transition and Readiness Requirements
These describe the higher-level needs of the organization as a whole, such as the business issues or opportunities, and reasons why a project has been undertaken.
Business Requirements
These describe the needs of a stakeholder or stakeholder group.
Stakeholder Requirements
These sessions are used in the software development industry. These facilitated sessions focus on bringing business SMEs and the development team together to gather requirements and improve the software development process.
Joint Application Design/Development (JAD)
This describes how individual requirements meet the business need for the project. Might start at a high level and become progressively more detailed. Before being baselined, must be unambiguous, traceable, complete, consistent, and acceptable to key stakeholders.
Requirements Documentation
This enhances brainstorming with a voting process used to rank the most useful ideas for further brainstorming or for prioritization. This is a structured form of brainstorming consisting of four steps:1. A question is posed to the group. Each person silently generates and writes down their ideas.2. The moderator writes down the ideas on a flip chart until all ideas are recorded.3. Each recorded idea is discussed until all group members have a clear understanding.4. Individuals vote privates to prioritize the ideas, (usually 1-5). Voting may take place in many rounds to reduce and focus in on ideas. After each round, votes are tallied and highest scoring ideas are selected.
Nominal Group Technique
Used to compare the baseline to the actual results and determine if it’s within the threshold amount or if corrective or preventative action is appropriate.
Variance Analysis
______ allow large numbers of ideas to be classified into groups for review and analysis.
Affinity Diagrams
______ bring together prequalified stakeholders and SMEs to learn about their expectations and attitudes about a proposed product, service, or result. A trained moderator guides the group through an interactive discussion designed to be more conversational than a one-on-one interview.
Focus Groups
______ consolidates ideas created through individual brainstorming sessions into a single map to reflect commonality and differences in understanding and to generate new ideas.
Mind Mapping
______ includes the processes required to ensure that the project includes all of the work required, and only the work required, to complete the project successfully. Managing the project scope is primarily concerned with defining and controlling what is and what is not included in the project.
Project Scope Management
______ involves comparing actual or planned products, processes, and practices to those of comparable organizations to identify best practices, generate ideas for improvement, and provide a basis for measuring performance. This can be internal or external.
Benchmarking
Project deliverables that are completed and checked for correctness through the Control Quality Process.
Verified Deliverables
