---
ref_id: PR05
ref_type: Process
ref_name: "Collect Requirements"
version: "1.0.0"
status: Active
pmbok8_source: "PMBOK8 Guide §2.2.2.2"
companion_ref_shortcode: PG-APG-5.3
related_skills:
  - SKL-03-02
  - SKL-02-03
related_artifacts:
  - A04
  - A07
  - A08
  - A13
  - A14
file_path: "reference/processes/PR05-collect-requirements.md"
---

# PR05 — Collect Requirements

**Ref ID:** PR05
**Type:** Process
**PMBOK8 Source:** §2.2.2.2
**Version:** 1.0.0

---

## Definition

Collect Requirements is the process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives.

## Key Characteristics

- **Requirement Transformation:** Elicits and translates vague stakeholder expectations into precise, actionable technical or business specifications.
- **Traceability Baseline:** Generates the Requirements Traceability Matrix (RTM) to link requirements from origin to ultimate validation.
- **Continuous Elicitation:** Performed periodically throughout the project life cycle, especially in adaptive, backlog-driven environments.
- **Prioritization Discipline:** Employs nominal group techniques, voting, or MoSCoW mapping to handle conflicting stakeholder interests.
- **Foundation Role:** Forms the essential basis for Define Scope, Create WBS, Plan Quality, and Plan Risk Management.

## PMBOK 8 Context

Under PMBOK 8, Collect Requirements falls squarely under the **Scope Performance Domain** but is highly dependent on the **Stakeholders Performance Domain**. Meaningful requirements collection requires structured stakeholder collaboration and communication. Elicited requirements are logged as detailed backlog items or hierarchical specifications, which form the groundwork for delivery verification.

## Inputs

| Input | Description | Source |
|---|---|---|
| Project Charter | Outlines the high-level project boundary, objectives, and early deliverables context. | PR01 Develop Project Charter |
| Scope & Requirements Plans | Establishes the governing methodology for how requirements will be collected and managed. | PR04 Plan Scope Management |
| Stakeholder Register | Provides a directory of stakeholders to consult for eliciting requirements. | PR02 Identify Stakeholders |
| Business Documents | Business case explaining the strategic mandate and intended benefits of the project. | Sponsoring Organization |
| Project Documents | Assumption logs and lessons learned to identify bounds or prior pitfalls. | Project Registry |

## Outputs

| Output | Description | Destination |
|---|---|---|
| Requirements Documentation | Detailed list of functional, non-functional, business, quality, and transition requirements. | A08 Scope and Requirements Backlog |
| Requirements Traceability Matrix | A grid mapping requirements from source, through design, to verified deliverables. | A13 Requirements Traceability Matrix |

## Tools and Techniques

- **Data Gathering:** Interviews, focus groups, questionnaires, surveys, and collaborative brainstorming.
- **Data Analysis:** Document analysis of existing business rules, system contracts, or industry standards.
- **Decision Making:** Voting, prioritization ranking, and nominal group techniques to reach consensus.
- **Data Representation:** Mind mapping and affinity diagrams to organize requirements categories logically.
- **Interpersonal Skills:** Facilitation, negotiation, active listening, and observation (shadowing).
- **Design Thinking:** Persona development and empathy mapping to discover latent user needs.

## Cross-References

| Related Item | Type | Relationship |
|---|---|---|
| A04 | Artifact | Source of high-level objectives and business parameters |
| A07 | Artifact | Directory of stakeholders to consult for eliciting requirements |
| A08 | Artifact | Registry for requirements in adaptive and hybrid environments |
| A13 | Artifact | Principal output grid establishing downstream traceability |
| PR02 | Process | Supplying the stakeholder register to direct elicitation efforts |
| PR04 | Process | Providing the governing plans that dictate the elicitation methodology |
| SKL-03-02 | Skill | Plan Scope and Requirements |

## Practitioner Notes

Practitioners executing this process should seek answers to the following vital questions:
1. Have all relevant stakeholders (internal, external, regulatory, end-user) been included as requirements sources?
2. Are requirements documented with sufficient specificity to be fully measurable, testable, and realistic?
3. How will conflicting requirements from different stakeholder groups be systematically prioritized and resolved?
4. Are requirements traceable from primary business objectives all the way to final deliverables and test cases?
5. How will requirements changes and progressive elaboration be managed throughout the delivery cycle?

## Change Log

| Version | Date | Description | Author |
|---|---|---|---|
| 1.0.0 | 2026-06-02 | Rebuilt to align with canonical REF file structure and YAML front-matter | PMO Director |

---

*Authority: PMBOK8 Guide §2.2.2.2; Process Groups Practice Guide §5.3*
