Requirements Documentation: Definition, Purpose, and Key Attributes

PMBOK v8 Definition

Requirements documentation is a description of how individual requirements should meet the business needs of the project. Requirements may start out at a high level and become progressively more detailed as more information about the requirements becomes known. Before being baselined, requirements should be unambiguous (measurable and testable), traceable, complete, consistent, and acceptable to key stakeholders. This documentation belongs to the Project Scope Management knowledge area and serves as a key output of the Collect Requirements process.

Why It Matters for the Exam

Requirements documentation appears frequently in PMI exam questions testing your understanding of scope management and quality attributes of requirements. Questions often focus on the characteristics that requirements must possess before baselining, the distinction between business and technical requirements, and how this documentation connects to the requirements traceability matrix. Expect situational questions where you must identify which requirement attribute is missing or violated.

Key Points to Remember (for the exam)

• Primary Purpose: Describes how individual requirements meet the business needs of the project
• Progressive Elaboration: Requirements start at a high level and become more detailed as information becomes known
• Pre-Baseline Attributes (MEMORIZE THIS): Requirements must be:
  • Unambiguous (measurable and testable)
  • Traceable
  • Complete
  • Consistent
  • Acceptable to key stakeholders
• Format Flexibility: Ranges from a simple document listing requirements categorized by stakeholder and priority, to more elaborate forms containing executive summary, detailed descriptions, and attachments
• Classification Types: Many organizations categorize into:
  • Business requirements: Stakeholder needs, strategic objectives, high-level organizational needs
  • Technical requirements: Determine how those needs will be implemented
• Additional Classifications: Stakeholder requirements (needs of a stakeholder or stakeholder group) and solution requirements
• Documentation Components: May include static or dynamic graphic information

Typical PMI Exam Example

A project manager is reviewing requirements documentation before submitting it for baseline approval. The sponsor asks whether each requirement can be verified through testing. Which requirement attribute is the sponsor questioning?

Answer: The requirement must be unambiguous (measurable and testable). The sponsor is checking if the requirements are testable, which is part of being unambiguous.

PMI Exam Traps

• Trap: Confusing requirements documentation with the requirements management plan

  • Reality: Requirements documentation describes what the requirements are; the requirements management plan describes how requirements activities will be planned, tracked, and reported

• Trap: Thinking all requirements must be fully detailed from the start

  • Reality: Requirements may start at a high level and become progressively more detailed. Progressive elaboration is expected

• Trap: Believing business requirements and technical requirements are interchangeable

  • Reality: Business requirements refer to stakeholder needs; technical requirements determine how those needs will be implemented. They are distinct but linked

• Trap: Assuming requirements documentation is a single fixed format

  • Reality: Format ranges from simple lists to elaborate documents with executive summaries, detailed descriptions, attachments, and graphic information

Important PMI Connections

Quick Review Questions

1. What five attributes must requirements possess before being baselined?

2. A stakeholder says "the system should be fast." Which requirement attribute is missing?

3. What is the difference between business requirements and technical requirements?

4. What is the minimum format for requirements documentation according to PMBOK v8?

5. How does requirements documentation relate to the requirements traceability matrix?

PMBOK v8 Reference

Section 4 – Inputs and Outputs (Requirements Documentation)
Related Sections: Collect Requirements process, Requirements Traceability Matrix, Requirements Management Plan