Project Scope Management Flashcards
Identify the six processes in the Project Scope Management knowledge area
Plan Scope Management
Collect Requirements
Define Scope
Create WBS
Validate Scope
Control Scope
Project scope management includes the processes required to ensure that the project includes all 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
The process of creating a scope management and requirements management plans that document how the project and product scope will be defined, validated, and controlled and how the requirements will be defined, managed and controlled.
Plan Scope Management Process
Outputs: Scope Management Plan, Requirements Management Plan
A subsidiary plan of the project or program management plan that describes how the scope will be defined, developed, monitored, controlled, and validated.
Scope Management Plan
A subsidiary plan of the project or program management plan that describes how requirements will be analyzed, documented, and managed.
Requirements Management Plan
The process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives
Collect Requirements Process
Requirements are the foundation of the project and must be comprehensive, including both product and project requirements
Key Outputs: Requirements Documentation, Requirements Traceability Matrix
An elicitation technique that brings together prequalified stakeholders and subject matter experts to learn about their expectations and attitudes about a proposed product, service, or result.
Focus Group
Used to collect requirements, focus groups gather representative feedback under the guidance of a facilitator.
Focused Sessions attended by key cross-functional stakeholders to define product requirements.
Facilitated Workshops
Example: joint application development or joint application design (JAD) sessions and quality function deployment (QFD) sessions. Facilitated workshops improve communication, commitment, and buy-in.
Creativity technique that allows participants to think and contribute creatively with minimal structure or boundaries.
Brainstorming
A technique that enhances brainstorming with a voting process used to rank the most useful ideas for further brainstorming or for prioritization.
Group Technique
A technique used to consolidate ideas created through individual brainstorming sessions into a single map to reflect commonality and differences in understanding and to generate new ideas
Mind Mapping
A technique that allows large number of ideas to be classified for review and analysis.
Affinity Diagram
AKA: “sticky note process”
Techniques used to select a course of action from different alternatives.
Voting Techniques
Plurality - largest group decides, even if majority is not reached
Majority - more than half the group agrees
Unanimity - everyone agrees.
Written sets of questions designed to quickly accumulate information from a large number of respondents.
Questionnaires and Surveys
Watching end-users do their work. Helpful when identifying difficult to articulate requirements. Also called job-shadowing or ghosting.
Observations
A method of obtaining early feedback on requirements by providing a working model of the expected product before actually building it
Prototype
Using prototypes aligns with and is a form of progressive elaboration
__________ is the comparison of 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.
Benchmarking
A visual depiction of the product scope showing a business system (process, equipment, computer systems, etc.), and how people and other systems (actors) interact with it.
Context Diagram
A description of how individual requirements meet the business need for the people.
Requirements Documentation
Serves as the basis and foundation for the project and is based on the gathered requirements. In agile/adaptive projects, the requirements are captured in the product backlog.
A grid that links the product requirements from their origin to the deliverables that satisfy them.
Requirements Traceability Matrix
Requirements may also be traced to: project scope, product design, WBS deliverables, test strategy and scenarios, etc.
The process of developing a detailed description of the project and product.
Define Scope Process
The project scope statement includes clearly defining the in-scope and out-of-scope requirements and the project deliverables.
The description of the project scope, major deliverables, assumptions, and constraints.
Project Scope Statement
Includes in-scope and out-of-scope requirements. The scope statement is a component of the scope baseline and may be progressively elaborated. Ideally, however, the scope is defines in as much detail as possible to minimize the occurrence of scope creep (unmanaged changes to the project scope).
In practice, many organizations refer to the scope statement as the “scope of work” or “statement of work”
The process of subdividing project deliverables and project work into smaller, more manageable components.
Create WBS Process
The project deliverables are composed into work packages using a graphical, hierarchical structure. Along with the WBS, there should be a WBS dictionary providing the back-end details of the work packages.
A technique used for dividing and subdividing the project scope and project deliverables into smaller, more manageable parts.
Decomposition
Is used to break the deliverables down into work packages (the lowest level of the WBS). Decomposition will also be used to break the work packages down into schedule activities in the Define Activities Process
Used in developing the WBS. The total of the lower level work rolls up to the higher levels. Nothing is left out and no extra work is completed
The 100% Rule
A management control point where scope, budget, actual cost, and schedule are integrated and compared to earned value for performance measurement.
Control Account
May contain multiple work packages, but each work package can only align with one control account, demonstrating a one-to-many relationship. They are typically the 2nd level of the WBS.
A hierarchical decomposition of the total scope of work to be carried out by the project team to create the required deliverables
Work Breakdown Structure (WBS)
The WBS is a component of the scope baseline
The work defined at the lowest level of the WBS for which cost and duration can be estimated and managed.
Work Package
The deliverables are decomposed to the work package level on a WBS. The work package owner is able to estimate, manage, and control the work of the work package, The work packages will be decomposed into schedule activities on the project schedule.
A document that provides detailed deliverable, activity, and scheduling information about each component in the WBS
WBS Dictionary
Is a component of the scope baseline
The approved version of a scope statement, WBS, and its associated WBS dictionary, that can be changed using formal change control procedures and is used as a basis for comparison to actual results.
Scope Baseline
The uncontrolled expansion to product or project scope without adjustments to time, cost, and resources.
Scope Creep
Formalizes acceptance of the completed project deliverables by the end-user, customer, or requesting party.
Validate Scope Process
Key output: Accepted Deliverables
Compare to Control Quality
A set of conditions that is required to be met before deliverables are accepted
Accepted Deliverables
Examination of a work product to determine whether it conforms to documented standards
Inspection (used in Validate Scope Process)
The process of monitoring the status of the project and product scope and managing changes to the scope baseline
Control Scope Process
A technique for determining the cause and degree of difference between the baseline and actual performance.
Variance Analysis
An analytical technique that uses mathematical models to forecast future outcomes based on historical results.
Trend Analysis
The performance data collected from controlling processes, analyzed in comparison with project management plan components, project documents, and other work performance information.
Work Performance Information
