Business Requirements Document (BRD)
A formal, structured record that specifies and details an organization’s business needs.
Key Points
- Defines what the business needs and why, not how the solution will be built.
- Includes objectives, scope, stakeholders, high-level processes, and acceptance criteria.
- Serves as a baseline for scope management and change control.
- Requires review and approval from key business stakeholders to ensure alignment.
Example
A bank plans to launch mobile check deposit. The BRD outlines the business goal (increase digital adoption by 20%), in-scope features (capture, review, submit), excluded items (foreign checks), stakeholders (retail banking, compliance), constraints (regulatory hold times), and acceptance criteria (99.5% successful deposit submissions).
PMP Example Question
Which document primarily captures the organization’s detailed business needs and expected outcomes to guide solution selection?
- Business Requirements Document (BRD)
- Software Requirements Specification (SRS)
- Project Charter
- Product Backlog
Correct Answer: A — Business Requirements Document (BRD)
Explanation: The BRD documents the business needs and desired outcomes. The SRS details system requirements, the charter authorizes the project at a high level, and the product backlog orders solution work items.
