A Business Requirement Document (BRD)
BRD is a formal contract between the organization and the customer for a product. By describing in full detail all the processes that should be implemented, a BRD is used through the entire cycle of the project to ensure that the product meets the detailed specifications and that the project gains value and achieves the desired results. If it is prepared for a technical product, the BRD also includes technical specifications.
In simpler terms, BRD indicates what the business wants to achieve.
It should include the following:
1. Project Scope
2. Problem Statement
3. Intended Audience
4. Decision Making and Approval Process
5. Background and Prior Project Information
6. Functional Requirements
7. Non Functional Requirements
8. Assumptions, Dependencies and Constraints
9. Risks and Risk Management Process
10. Solution Options
11. Change Management Process
12. Appendices
13. Approvals
14. Checklists (Process and Requirements)
Advantages of BRD:
• To gain agreement among all stakeholders
• To provide a foundation to communicate to a technology service provider what the solution needs to do to satisfy the customer’s and business’ needs
• To provide input into the next phase for this project
• To describe how the customer/business needs will be met by the solution
