HKSM
Requirements Documentation
A documented explanation showing how each requirement aligns with and fulfills the project's business needs and objectives.
Key Points
- Details each requirement with description, rationale, priority, acceptance criteria, source, and traceability to business needs.
- Becomes the approved baseline for requirements; any changes go through integrated change control.
- Supports validation and verification by linking requirements to objectives, tests, and acceptance criteria.
- Guides scope definition and stakeholder alignment by clarifying what is needed and why.
Example
In a payroll system upgrade, requirement R-17 "calculate overtime per union rules" is mapped to the business need "reduce payroll errors by 50%." The documentation lists acceptance criteria (zero calculation defects across two payroll cycles), priority (High), source (HR), and references to related test cases and WBS work packages.
PMP Example Question
Which artifact specifically explains how each individual requirement satisfies the project's business need?
- Business case
- Requirements management plan
- Requirements documentation
- Project charter
Correct Answer: C — Requirements documentation
Explanation: Requirements documentation captures each requirement and shows its alignment to the business need. The business case defines the need at a high level, the management plan explains how requirements will be managed, and the charter authorizes the project.
