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].
Test your knowledge
Practice scenario-based questions on this topic with detailed explanations.