Define Scope
Define Scope is the process of developing a detailed description of the project and product, resulting in the project scope statement.
Explanation
Define Scope takes the requirements documentation, project charter, and other inputs and refines them into a detailed project scope statement. This process involves selecting the final project requirements from the requirements documentation, analyzing them in detail, and developing a clear description of the project and its major deliverables, assumptions, and constraints.
Key tools and techniques include expert judgment, data analysis, decision making, interpersonal and team skills, and product analysis. Product analysis techniques such as product breakdown, systems analysis, requirements analysis, systems engineering, value analysis, and value engineering help translate high-level product descriptions into tangible deliverables.
The primary output is the project scope statement, which describes in detail the project deliverables and the work required to create them. It also includes explicit project exclusions, which are equally important because they clarify what is not part of the project. A well-crafted scope statement reduces ambiguity and sets clear expectations for all stakeholders.
Key Points
- •Develops a detailed description of the project and product
- •Primary output is the project scope statement
- •Uses product analysis, expert judgment, and decision making
- •Explicitly documents project exclusions
Exam Tip
Define Scope produces the project scope statement, not the WBS. The WBS is created in the next process, Create WBS. Know the sequence of scope processes.
Frequently Asked Questions
Related Topics
Project Scope Statement
The project scope statement is a detailed description of the project scope, major deliverables, assumptions, and constraints that provides a documented basis for making future project decisions.
Collect Requirements
Collect Requirements is the process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives.
Product Analysis
Product analysis is a set of techniques used in the Define Scope process to translate product descriptions and objectives into tangible deliverables and requirements.
Create WBS
Create WBS is the process of subdividing project deliverables and project work into smaller, more manageable components.
Most-studied PMP concepts
High-yield topics our learners drill most before exam day.
Burndown Chart
A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.
Resource Leveling
Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.
Risk Register
The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.
Stakeholder Mapping
Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.
Relative Estimation
Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.
Cost Performance Index (CPI)
Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.
Schedule Performance Index (SPI)
Schedule Performance Index (SPI) is an EVM efficiency metric that measures schedule performance as the ratio of earned value to planned value: SPI = EV / PV.
Earned Value Management (EVM)
Earned Value Management (EVM) is a methodology that integrates scope, schedule, and cost data to assess project performance and progress objectively.
Power/Influence Grid
The power/influence grid is a stakeholder classification model that groups stakeholders based on their level of authority (power) and their active involvement or ability to affect the project (influence).
Part of
Scope Management
Test your knowledge
Practice scenario-based questions on this topic with detailed explanations.