Tag Archives: requirement document

BRD: Really a Need or Time-Crusher?

BRD: Really a Need or time-crusher?

BRD-timecrush1BRD-timecrush2As a BA the one thing which strikes in our mind is to design a high a quality BRD (Business Requirement Document). In my last post I have written an overview of BRD which includes the features of a good quality BRD. Few days back I was attending a webinar on the same topic in which the presenter was discussing all the details. It was really interesting to know that BAs devote most of their times in designing an easy to understand document which contains business requirements. A BA first discusses the details with different stakeholders do the brain storming and then designs a document using all his writing skills to make it as simple as possible so that the others can understand the requirement and the project can run smoothly…. Oh God how much intelligence required in that!

But this all gave me a thought that after designing a document of 100+ pages with all the efforts to include the business requirements will the document find the intended audience? Will that document find space in the INBOX, which is usually flooded with other mails (in a survey it was found that the business decision makers usually get 85+ mails per day), of the stakeholders and will all of them spare their time in reading those 100+ pages? I think NO. So if the answer to this is no, then why BAs are devoting their time in designing BRDs. Documenting a requirement sheet will require tremendous efforts in organizing, double-checking, typing, copying, pasting etc which will turn out as 85% of clerical job and in turn it will reduce the strategic competence of a BA. Thus it can be accepted that a BA who is sparing 85% of his energy in doing clerical job can’t make impact on the organization with his strategic skills. Continue reading

Business Requirements Document: An Overview

Business Requirements Document (BRD)

BRD-documentBRD, an acronym of Business Requirements Document is widely accepted structured document for project requirements which defines what should be delivered in order to gain value in the project. This document is designed to assist with the project management and the implementation during the entire life cycle of the project. Business requirements are consist of both functional and non-functional requirements which lead to creation or update of product, system or a software. BRD mainly emphasize on what should be the end result and it doesn’t bother how the objective is achieved.

There are many variants of BRD known to people like SRS (System Requirement Specification) or SRD (System Requirement Document) and FSD (Functional Specification Document). BRD can be described as a mode of communication in completion of a project. The main objectives of a BRD are as below:

 

  1. It should be simple and all the involved stakeholders should agree to it.
  2. It should contain more business requirements rather than technical requirements, as the main motto of a BRD is what to achieve and not how to achieve.
  3. It should describe the business needs in clear and concise manner.
  4. It should have a logical flow and can be used as an input for next phase of the project.

Continue reading