HKSM
Business Requirement Documents (BRD)
A document that compiles the full set of business requirements for a specific project and establishes the agreed scope of what must be delivered.
Key Points
- Lists all agreed business requirements, both functional and nonfunctional, with clear acceptance criteria.
- Acts as a scope baseline and supports traceability and change control throughout the project.
- Developed with business stakeholders and approved to confirm shared understanding and commitment.
- In agile or hybrid work, the BRD may be represented by a prioritized backlog of user stories and criteria.
Example
On an e-commerce upgrade, the team produces a BRD that includes requirements such as enabling guest checkout, supporting two payment providers, page load under 2 seconds for 95 percent of users, and order confirmation emails within 1 minute. When a stakeholder requests adding a new loyalty feature mid-project, the change is evaluated against the BRD to assess scope, impact, and priority.
PMP Example Question
Which artifact provides the complete, approved set of business needs used to baseline scope and guide acceptance testing?
- Project charter
- Business Requirement Documents (BRD)
- Work breakdown structure (WBS)
- Risk register
Correct Answer: B — Business Requirement Documents (BRD)
Explanation: The BRD consolidates all business requirements and acceptance criteria. The charter authorizes the project, the WBS decomposes scope, and the risk register lists risks.
