top of page
DiiT
EUROPE | UK | CANADA | AFRICA | UAE
UK Consulting
WELCOME TO THE PRACTICAL
SECTION FOR
BUSINESS REQUIREMENT DOCUMENTATION (BRD)
Before we commence on working on a practical Business Requirement Document (BRD), read through the information below 1st
What is a Business Requirement Document all about?
A business requirements document describes all the requirements elicited/ gotten from the stakeholders for a project (i.e., what a new or updated product/ page should do), including the user's needs and expectations, the purpose behind this solution, and any high-level constraints that could impact a successful deployment.
It clearly defines everything that a project entails. It considers all facets of the project, including the expected outcomes and the key stakeholders.
What does a good BRD contain?
A properly documented BRD must have amongst everything else 7/8 key sections within it
1. An executive summary
2. Project Objectives
3. A need/ problem statement
4. Project Scope
5. Requirements
6. Key Stakeholders
7. Project Constraints
8. Schedule/ timeline/ milestones
By going through the various Project Initiation Document (PID), Produce the BRD. You are allowed to assume your high-level requirements and define your low-level/ detailed requirements.
NOTE:
For any Requirement Documentation task you intend to deliver the deliverables for, get in touch with Ese or the admin about it, so as to create awareness of your task for review/ approval purposes.
Project Initiation Document (PID)
Project 1
Project Initiation Document (PID)
Project 2
Project Initiation Document (PID)
Project 3
Business Requirement Document (BRD) Template
Requirement Catalogue Template
bottom of page