ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
2
BUSINESS REQUIREMENTS DOCUMENT TEMPLATE
3
PROJECT DETAILS
4
PROJECT NAMEDOCUMENT #
5
6
CREATORDATE
7
8
VERSION #
9
10
11
1. EXECUTIVE SUMMARY SNAPSHOT
12
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:
- What is the goal (purpose) of this business requirements document (BRD)?
- Who is the audience for this business requirements document?
13
14
15
2. PROJECT DESCRIPTION
16
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.
17
18
19
3. PROJECT SCOPE
20
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.
21
22
IN-SCOPE ITEMSOUT-OF-SCOPE ITEMS
23
Item 1:Item 1:
24
Item 2:Item 2:
25
Item 3:Item 3:
26
Item 4:Item 4:
27
Etc.
28
29
4. BUSINESS DRIVERS
30
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.
31
Business Driver 1:Provide a detailed explanation for this driver...
32
Business Driver 2:Provide a detailed explanation for this driver…
33
Business Driver 3:Provide a detailed explanation for this driver…
34
Business Driver 4:Provide a detailed explanation for this driver…
35
36
5. PRESENT PROCESS
37
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.
38
39
40
6. PROPOSED PROCESS
41
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. For this process, we recommend that you use the same illustrative tool/style that you used for your present/current process (above).
42
43
44
7. FUNCTIONAL REQUIREMENTS
45
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.
46
47
48
PRIORITY
49
Use the following priority table. It allows you to apply a ratings system to your requirements, so you have the visibility (into the value, status, and description of each requirement) that's necessary for determining whether a particular requirement is essential to project success:
50
VALUESTATUSDESCRIPTION
51
1ImmediateThe requirement is critical to the project’s success. Without fulfilling this requirement, the project is not possible.
52
2HighThe requirement is high priority re the project's success, but the project could still be implemented in a minimum viable product (MVP) scenario.
53
3ModerateThe requirement is important to the project’s success, as it provides value, but the project could still be implemented in an MVP scenario.
54
4LowThe requirement is of low priority, but the project’s success is not dependent upon it.
55
5ProspectiveThe requirement is out of the project’s scope and is included as a possible component of a prospective release and/or feature.
56
57
CATEGORIES (RC1)
58
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. The following table includes a unique ID for each requirement, the details of each requirement, the priority of each requirement, and the name of the person who is driving or is responsible for the requirement. Include descriptions of how the current process addresses the issue. Also include the functional requirements necessary to achieve success.
59
IDREQUIREMENTPRIORITYRAISED BY
60
61
62
63
64
65
66
8. NON-FUNCTIONAL REQUIREMENTS
67
Detail all non-functional requirements (NFRs) of the project, including such things as features, system behavior, and project characteristics that relate to user experience.
68
IDREQUIREMENT
69
70
71
72
73
74
75
9. GLOSSARY
76
For easy reference, enter any terms, abbreviations, and/or acronyms that you include in this document.
77
TERM/ABBREVIATIONEXPLANATION
78
79
80
81
82
83
84
10. REFERENCES
85
Provide links to all referenced resources (websites, documents, etc.) throughout this document.
86
NAMELOCATION
87
88
89
90
91
11. APPENDIX
92
Include any additional information for reference, e.g., process details, analysis results, studies, third-party examples, etc.
93
94
95
CLICK HERE TO CREATE IN SMARTSHEET
96
97
98
99
100