Collect Requirements
Foundational concept
Not named in the current ECO. Still worth knowing — it underpins the situational questions and PMI's own experience verification uses the process groups.
Collect Requirements is the process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives.
Know it well enough for the exam? Questions on Collect Requirements are scenario-based, not definitional.
Practice it freeExplanation
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, simple description of a feature or requirement written from the perspective of the end user, 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 plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.
Burn-Up Chart
A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.
Resource Leveling
Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.
Deliverables
A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.
Power Interest Grid (Power/Influence Grid)
The power interest grid is a 2x2 stakeholder mapping tool that plots each stakeholder by power (ability to affect the project) and interest (concern about its outcome) to decide how to engage them: manage closely, keep satisfied, keep informed, or monitor.
Critical Path Method (CPM)
The Critical Path Method (CPM) is a schedule network analysis technique that calculates early and late start and finish dates for every activity to find the longest path through the project, the minimum project duration, and the float on every other path.
Weighted Shortest Job First (WSJF)
Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.
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.
Part of
Scope Management
Practice Collect Requirements
Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.