<aside> <img src="/icons/meeting_gray.svg" alt="/icons/meeting_gray.svg" width="40px" /> The Project BRD template is a part of the comprehensive Notion for Project Management Template that has 30+ pages/databases which covers all phases of Project management. For more details check out the following gumroad shop or visit the NotionMarkethub website.
</aside>
<aside> <img src="/icons/arrow-right-basic_gray.svg" alt="/icons/arrow-right-basic_gray.svg" width="40px" /> Project Title: __________ Prepared by: __________ Reviewed by: __________
Approved by: __________
**Date**: __________
</aside>
<aside> <img src="/icons/arrow-right-basic_gray.svg" alt="/icons/arrow-right-basic_gray.svg" width="40px" /> Provide an executive summary (overview of your business requirements) here. Your executive summary should be a “snapshot” of the purpose of your business requirements, including a brief description of any analysis, findings, project details, scope, business drivers, proposed process, current process, and functional requirements. An executive summary provides an overview of a larger document or of research and is usually the first thing your reader will see. Here are the questions you should answer when writing your business requirements executive summary:
<aside> <img src="/icons/arrow-right-basic_gray.svg" alt="/icons/arrow-right-basic_gray.svg" width="40px" /> In this section, describe the project for which you are writing this business requirements document. Describe the project’s purpose, what the current process/solution is for the project, what the challenges are, and why you need to undertake the project.
</aside>
<aside> <img src="/icons/arrow-right-basic_gray.svg" alt="/icons/arrow-right-basic_gray.svg" width="40px" /> Provide a high-level description of the project’s scope, including a list of project-specific goals, tasks, deliverables, costs, deadlines -- everything that is “in” and “out” of scope for the project. This information provides team members with guidelines for the scope of the project, so they can plan and resource accordingly.
| IN-SCOPE ITEMS | OUT-OF-SCOPE ITEMS |
|---|---|
| Item 1: | Item 1: |
| Item 2: | Item 2: |
| Item 3: | Item 3: |
| Item 4: | Item 4: |
| </aside> |
<aside> <img src="/icons/arrow-right-basic_gray.svg" alt="/icons/arrow-right-basic_gray.svg" width="40px" /> Enter the reasons (i.e., business drivers) why your business is initiating the project. In short, Why are you undertaking the project? Examples might include the following: legal requirements, cost savings with a more efficient practice, updated import/export laws, improved efficiency, improved sales, etc.
| Business Driver 1: | Provide a detailed explanation for this driver... |
|---|---|
| Business Driver 2: | Provide a detailed explanation for this driver… |
| Business Driver 3: | Provide a detailed explanation for this driver… |
| Business Driver 4: | Provide a detailed explanation for this driver… |
| </aside> |
<aside> <img src="/icons/arrow-right-basic_gray.svg" alt="/icons/arrow-right-basic_gray.svg" width="40px" /> Provide details of your current, prevailing process for addressing the primary issue your project attempts to solve. Feel free to include diagrams, flowcharts, or other visuals to illustrate the current process.
<aside> <img src="/icons/arrow-right-basic_gray.svg" alt="/icons/arrow-right-basic_gray.svg" width="40px" /> Provide details of the proposed process for addressing the primary issue your project attempts to solve. Feel free to include diagrams, flowcharts, or other visuals to illustrate the proposed process.
<aside> <img src="/icons/arrow-right-basic_gray.svg" alt="/icons/arrow-right-basic_gray.svg" width="40px" /> Detail the project’s functional requirements by enumerating the ways in which the current process addresses the issue and by describing the functional requirements necessary to make the project successful .
<aside> <img src="/icons/arrow-right-basic_gray.svg" alt="/icons/arrow-right-basic_gray.svg" width="40px" /> In this section, detail the project’s functional use; break down your project’s requirements into categories so that they’re easy to understand. You can duplicate this section for any successive project categories as needed.
| ID | REQUIREMENT | PRIORITY | RAISED BY |
|---|---|---|---|
</aside>