1. What is BRD? How is it different from SRS?

Related Articles

what are the project priorities? Why this is important ? How to handle this ? 

2 days ago

What are the elicitation techniques using in a project?

2 days ago

What is requirement prioritization in Business analysis?

2 days ago

What is BRD

A Business Requirement Document (BRD) is report or document which is prepared to define the objectives or Requirements of a Project or a new Solution. It describes how the project will work. Or what output is expected from this solution. BRD gives the broader idea about how this solution will help in development of the core business. Once BRD is finalised and approved, stakeholders get complete clarity about the project, which removes the ambiguity and the further project development become easy. So, BRD is the most  important document for any project in the initial stage. Defining the correct goal, correct requirements is the key factor for any good BRD.

Who writes BRD-

Normally Business Analyst prepares BRD

Benefits of BRD-

BRD is prepared before projects starts in order to get all stakeholder on same page regarding key requirements , and how the project will look like.

So, Business Requirement Document:

1. Give complete overview of project or business solution, keeping everyone on same page, regarding all requirements , expectations , and what will be the final output of this solution and how this solution will be helpful in achieving the business goal.
2. Manages the requirement gathering in effective manner prior to project execution, so that all client expectations are met without any ambiguity.
3. Defines the project scope which will be roadmap to all stakeholders regarding cost and timelines
4. Helps in tracking the progress of project during its life cycle.

 

Few important element and Steps in  writing BRD:

1. Business Goal

Business goal should be clearly specified here. What is current process, and where the business will be with new proposed solution.

We can use SMART technique to specify the goal. The goal should be Specific, Measurable, Achievable, Relevant, and completed within time.

2. Business Objectives:

Business goal is then further divided into certain functionalities which are called as business objectives. How the user will interact with system, how system will respond, how result will be shown, what will be the final output, these all will come under business objectives.

3. Business Rules:

New project solution will follow certain business rules, which need to be defined here. For example, how data will flow, how the output will be displayed, administrative rights, etc

4. Background-

Here existing process is explained. And whatever drawbacks in existing process are being tried to overcome in proposed process solution. So, it give clear idea of what will be the final output of the project.

Here SWOT Analysis will help to prepare AS Is and TO Be process.

5. Requirement Gathering

Very important steps in BRD. Clear and detailed requirement gathering will help in smoother project execution with expected result. Ensuring participation of maximum stakeholders and documenting the requirements in correct manner will build trust in project life cycle.

6. Identify Stakeholders

After finalising the requirement, we have to identify the stakeholders. And need to fix the roles and responsibility for each stakeholder. We can use RACI matric for stakeholder management.

7. Project Scope

In scope Functionality – Process flow about how the project works, start to end and user wise functionality.

Out scope Functionality- How the solution will perform outside the system, how other users will connect with this system.

8. TimeFrame- Define specific timeframe for the completion. It will help, keeping stakeholders focused towards goal. Periodic review will ensure to complete the project within agreed timeline
9. Project Budget – Define Project estimate considering business type, no of resources, systems, servers, etc
10. Assumptions- Define the assumptions which are to be followed by stakeholders throughout the project
11. Constraints – make stakeholders aware about the limitations / constraints of the project, so the people will be equipped to counter the challenges coming as obstacle.

What is SRS?

 

Software Requirement Specification (SRS) document is the complete document about how the software will perform. It is useful to developers team to understand the process flow. Here all the functional and non-functional requirements are documented alongwith the user interface with system using use cases.

 

SRS is prepared by system analysts or Business analysts and referred by development or implementation team.

 

Difference between BRD and SRS

1. BRD includes all business requirements , goal, objectives, project scope, stakeholders WHEREAS SRS includes functional and non-functional requirements being used for software development
2. BRD document is prepared during analysis phase of project WHEREAS SRS document is prepared at Planning Phase of project
3. BRD document is used by stakeholders and business users WHEREAS SRS document is sued by Developers / SMEs