Scope Management Flashcards
Plan Scope Management
2.2.1 (Planning Process Group, Scope Management)
Process of creating a scope management plan that documents how the project scope will be defined, validated, and controlled
Inputs: Project Charter, Project Management Plan, EEF, OPA
Tools & Techniques: Expert Judgement, Data Analysis, Meetings
Outputs: Scope Management Plan, Requirements Management Plan
Collect Requirements
2.2.2 (Planning Process Group, Scope Management)
Process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives
Inputs: Project Charter, Project Management Plan, Project Documents, Business Documents, Agreements, EEF, OPA
Tools & Techniques: Expert Judgement, Data Gathering, Data Analysis, Decision Making, Data Representation, Interpersonal and Team Skills, Content Diagram, Prototypes
Outputs: Requirements Documentation, Requirements Traceability Matrix
Define Scope
2.2.3 (Planning Process Group, Scope Management)
Process of developing a detailed description of the project and product
Inputs: Project Charter, Project Management Plan, Project Documents, EEF, OPA
Tools & Techniques: Expert Judgement, Data Analysis, Decision Making, Interpersonal and Team Skills, Product Analysis
Outputs: Project Scope Statement, Project Documents Updates
Create WBS
2.2.4 (Planning Process Group, Scope Management)
Process of subdividing project deliverables and project work into smaller, more manageable components
Inputs: Project Management Plan, Project Documents, EEF, OPA
Tools & Techniques: Expert Judgement, Decomposition
Outputs: Scope Baseline, Project Documents Updates
Validate Scope
4.2.5 (Monitoring & Controlling Process Group, Scope Management)
Process of formalizing acceptance of the completed project deliverables
Inputs: Project Management Plan, Project Documents, Verified Deliverables, Work Performance Data
Tools & Techniques: Inspection, Decision Making
Outputs: Accepted Deliverables, Work Performance Information, Change Requests, Project Documents Updates
Control Scope
4.2.5 (Monitoring & Controlling Process Group, Scope Management)
Process of monitoring the status of the project and product scope and managing changes to the scope baseline
Inputs: Project Management Plan, Project Documents, Work Performance Data, OPA
Tools & Techniques: Data Analysis
Outputs: Work Performance Information, Change Requests, Project Management Plan Updates, Project Documents Updates
Product Scope
Features and functions that characterize a product, service, or result
Project Scope
Work performed to deliver a product, service, or result with the specified features and functions. The term scope is sometimes viewed as including product scope.
Scope Creep
Uncontrolled changes that cause the project team to do extra work
Interviews
2.2.2. TT (Collect Requirements)
Formal or informal approach to elicit information from stakeholders by talking to them directly
Facilitated Workshops
2.2.2. TT (Collect Requirements)
Focused sessions that bring key stakeholders together to define product requirements
Focus Groups
2.2.2. TT (Collect Requirements)
Bring together prequalified stakeholders and subject matter experts to learn about their expectations and attitudes about a proposed product, service, or result. Moderator guides the group through interactive discussion, designed to be more conversational than a one-on-one interview.
Unanimity
2.2.2. TT (Collect Requirements)
Group Decision-Making Technique
Everyone agrees on the decision
Majority
2.2.2. TT (Collect Requirements)
Group Decision-Making Technique
More than half the people in the group agree on the decision
Plurality
2.2.2. TT (Collect Requirements)
Group Decision-Making Technique
Idea that gets the most votes wins
Dictatorship
2.2.2. TT (Collect Requirements)
Group Decision-Making Technique
One person makes the decision for the whole group
Idea/Mind Maps
2.2.2. TT (Collect Requirements)
Group Creativity Techniques
Ideas crated through indiivdual brainstorming sessions are consolidated into a single map to reflect commonality and differences in understanding, and generate new ideas.
Brainstorming
2.2.2. TT (Collect Requirements)
Group Creativity Techniques
Used to generate and collect multiple ideas related to a project and product requirements. It does not include voting or prioritization, but it’s often used with other group creativity techniques that do.
Nominal Group Technique
2.2.2. TT (Collect Requirements)
Group Creativity Techniques
Enhances brainstorming with a voting process used to rank the most useful ideas for further brainstorming or for prioritization
Affinity Diagram
2.2.2. TT (Collect Requirements)
Group Creativity Techniques
Allows large numbers of ideas to be classified into groups for review and analysis
Multicriteria Decision Analysis
2.2.2. TT (Collect Requirements)
Group Creativity Techniques
Utilizes 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.
Questionnaires and Surveys
2.2.2. TT (Collect Requirements)
Written sets of questions designed to quickly accumulate information from a large number of respondents
Observations
2.2.2. TT (Collect Requirements)
A direct way of viewing individuals in their environment and how they perform their jobs or tasks and carry out processes
Prototypes
2.2.2. TT (Collect Requirements)
Method of obtaining early feedback on requirements by providing a working model of the expected product before actually building it
Benchmarking
2.2.2. TT (Collect Requirements)
Comparing actual or planned practices, such as processes and operations, to those of comparable organizations to identify best practices, generate ideas for improvement, and provide a basis for measuring performance. Those organizations can be internal or external.
Context Diagrams
2.2.2. TT (Collect Requirements)
Example of a scope model.
Visually depict the product scope by showing a business system (process, equipment, computer system, etc), and how people and other systems interact with it.
Show inputs to the business system, the actors providing the input, the outputs from the business system, and the actors receiving the output.
Document Analysis
2.2.2. TT (Collect Requirements)
Used to elicit requirements by analyzing existing documentation and identifying information relevant to the requirements.
Documents = business plans, marketing literature, agreements, requests for proposal, current process flows, logical data models, business rules repositories, application software documentation, business process or interface documentation, use cases, problem/issue logs
Requirements Document
2.2.2 Collect Requirements Output
Describes how individual requirements meet the business need for he project. Components: - Business Requirements - Stakeholder Requirements - Solution Requirements - Project Requirements
Requirements Traceability Matrix
2.2.2 Collect Requirements Output
Grid that links product requirements from their origin to the deliverables that satisfy them
Tracing Requirements for the following:
- Business needs, opportunities, goals, objectives
- Project objectives
- Project scope/WBS deliverables
- Product design
- Product development
- Test strategy and test scenarios
- High-level requirements to more detailed requirements
Alternatives Generation
2.2.3 Define Scope TT
Technique used to develop as many potential options as possible in order to identify different approaches to execute and perform the work of the project
Product Analysis
2.2.3 Define Scope TT
Translating high level descriptions of the product into project work that needs to be done/tangible deliverables
Project Scope Statement
2.2.3 Define Scope Output (part of Scope baseline)
Description of the project scope, major deliverables, assumptions, and constraints.
- Product scope description
- Acceptance criteria
- Deliverable
- Project exclusion
- Constraints
- Assumptions
Acceptance Criteria
2.2.3 Components of Project Scope Statement (which is a Define Scope Output)
Set of conditions that is required to be met before deliverables are accepted
Project Exlusion
2.2.3 Components of Project Scope Statement (which is a Define Scope Output)
Generally identifies what is excluded from the project (helps manage stakeholder expectations)
Constraints
2.2.3 Components of Project Scope Statement (which is a Define Scope Output)
Limiting factor that affects the execution of a project or process
Assumptions
2.2.3 Components of Project Scope Statement (which is a Define Scope Output)
Factor in the planning process that is considered to be true, real, or certain, without proof or demonstration
Decomposition
2.2.4 Create WBS TT
Technique used for dividing and subdividing the project scope and project deliverables into smaller, more manageable parts.
Work Breakdown Structure
2.2.4 Create WBS (part of scope baseline, an output of this process)
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.
- Doesn’t show the order of the work packages or dependencies between them
- Its only goal is to show the work involved in creating product
Work Package
2.2.4 Create WBS (important term)
The lowest level of WBS components
Scope Baseline
2.2.4 Create WBS Output
The approved version of a scope statement, WBS, and its associated WBS dictionary, that can be changed only through formal change control procedures and is used as a basis for comparison.
WBS Dictionary
2.2.4 Create WBS (part of the Output of Scope Baseline)
Document that provides detailed deliverable, activity, and scheduling information about each component in the WBS.
Control Accounts
2.2.4 Create WBS (term to know)
A tool that your company’s management and accountants use to track the individual work packages.
Variance Analysis
4.2.6 Control Scope TT
Technique for determining the cause and degree of difference between the baseline and actual performance.
Project performance measurements are used to assess the magnitude of variation from the original scope baseline.
Formal Acceptance
4.2.5 Validate Scope Term
You have written confirmation from all stakeholders that the deliverables match the requirements and the Project Management plan
Inspection
4.2.5 Validate Scope TT
Activities such as measuring, examining, and validating to determine whether work and deliverables meet requirements and product acceptance criteria
