0% found this document useful (0 votes)
2K views6 pages

BRD Template

This document is the Business Requirements Document (BRD) for an unnamed project. It provides high-level details about the project, including an overview, stakeholders, assumptions, and user stories. The BRD defines the requirements for the project and will be used to guide solution design, testing, determining completion, and assessing success. It includes sections for project details, a glossary of terms, and elaborates on key business requirements.

Uploaded by

Imtiyaz Shaikh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
2K views6 pages

BRD Template

This document is the Business Requirements Document (BRD) for an unnamed project. It provides high-level details about the project, including an overview, stakeholders, assumptions, and user stories. The BRD defines the requirements for the project and will be used to guide solution design, testing, determining completion, and assessing success. It includes sections for project details, a glossary of terms, and elaborates on key business requirements.

Uploaded by

Imtiyaz Shaikh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 6

[Insert Project Name]

Business Requirements Document (BRD)


Version i

VERSION AND APPROVALS


UTORS
VERSION HISTORY
Version #

Date

Revised By

Reason for change

This document has been approved as the official Business Requirements Document for <project name>,
and accurately reflects the current understanding of business requirements. Following approval of this
document, requirement changes will be governed by the projects change management process, including
impact analysis, appropriate reviews and approvals.

DOCUMENT APPROVALS
Approver Name

Project Role

Signature/Electronic Approval

Date

TABLE OF CONTENTS
VERSION AND APPROVALS.........................................................................................II
PROJECT DETAILS....................................................................................................2
OVERVIEW...............................................................................................................2
DOCUMENT RESOURCES..........................................................................................2
GLOSSARY OF TERMS..............................................................................................2
PROJECT OVERVIEW................................................................................................2
4.1 Project Overview and Background.................................................................................................... 2
4.2 Project Dependencies....................................................................................................................... 3
4.3 Stakeholders..................................................................................................................................... 3

KEY ASSUMPTIONS AND CONSTRAINTS.....................................................................3


5.1 Key Assumptions and Constraints.................................................................................................... 3

USER STORIES.........................................................................................................3
BUSINESS REQUIREMENTS ELABORATION..................................................................4
BUSINESS REQUIREMENTS ELABORATION..................................................................4
SAMPLE SCREEN/REPORT........................................................................................4

PROJECT DETAILS
Project Name
Project Type
Project Start Date
Project End Date
Project Sponsor
Primary Driver
Secondary Driver
Division
Project Manager/Dept

Enter Project Name

(e.g. New Initiative or Phase II)

(e.g. Mandatory or Efficiency)

OVERVIEW
This document defines the high level requirements [insert project name]. It will be used as the basis
for the following activities:

Creating solution designs


Developing test plans, test scripts, and test cases
Determining project completion
Assessing project success

DOCUMENT RESOURCES
Name

Business Unit

Role

<Identify all stakeholders


and resources involved
in gathering
requirements>

GLOSSARY OF TERMS
Term/Acronym

Definition

<Identify any terms and acronyms


used within this document>

PROJECT OVERVIEW
4.1 Project Overview and Background
<This information can be taken from the Project Charter. This is a brief description of what the
project is about. It includes the current situation, the problem and the objectives. This section serves
as the vision statement for the requirements. Each requirement should bring the project closer to the
vision.>

4.2 Project Dependencies


<List any related known projects that relate in whole or in part, or has a dependency on this project.>

4.3 Stakeholders
The following comprises the internal and external stakeholders whose requirements are represented
by this document:
Stakeholders

1.
2.
3.

KEY ASSUMPTIONS AND CONSTRAINTS


5.1 Key Assumptions and Constraints
#

Assumptions
List any assumptions the requirements are based on

Constraints
List any constraints the requirements are based on

USER STORIES

BUSINESS REQUIREMENTS ELABORATION


The following sections document the various business requirements of this module.

SAMPLE SCREEN/REPORT

You might also like