Collect Requirements
Collect Requirements is the process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives.
Explanation
Collect Requirements is a critical planning process that bridges the gap between high-level stakeholder expectations and the detailed project scope. Effective requirements collection ensures that the project team understands what stakeholders truly need, reducing the risk of rework, scope creep, and stakeholder dissatisfaction later in the project.
The process employs a wide range of tools and techniques including interviews, focus groups, facilitated workshops, questionnaires, benchmarking, brainstorming, nominal group technique, affinity diagrams, mind mapping, prototypes, and context diagrams. In agile environments, user stories and the product backlog serve as the primary requirements artifacts.
The two key outputs are requirements documentation and the requirements traceability matrix. Requirements documentation captures all requirements in sufficient detail for measurement and management, while the traceability matrix links each requirement back to its business objective and forward to the deliverables that satisfy it.
Key Points
- •Determines and documents stakeholder needs and requirements
- •Uses interviews, workshops, brainstorming, prototypes, and more
- •Outputs include requirements documentation and the traceability matrix
- •In agile, user stories and the product backlog capture requirements
Exam Tip
Know the many tools used in Collect Requirements. PMI frequently tests nominal group technique (voting/ranking after brainstorming) and the difference between interviews, focus groups, and facilitated workshops.
Frequently Asked Questions
Related Topics
Requirements Documentation
Requirements documentation describes how individual requirements meet the business need for the project, capturing all requirements in enough detail for them to be measured and managed.
Requirements Traceability Matrix
A requirements traceability matrix (RTM) is a grid that links product requirements from their origin to the deliverables that satisfy them, ensuring each requirement adds business value and is tracked throughout the project.
Requirements Management Plan
The requirements management plan is a component of the project management plan that describes how requirements will be analyzed, documented, and managed throughout the project.
User Stories
A User Story is a short, informal description of a feature told from the perspective of the person who desires the new capability, typically following the format: As a [role], I want [goal], so that [benefit].
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.