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

Risk Analysis

Business Analyst Techniques #2 Risk Analysis

Risk AnalysisRisk analysis or risk assessment is done to determine if the proposed project carries more risk than the organization is willing to bear. It helps in adjusting the cost and profit projections on the basis of the risks identified at any point. No project comes without risk and it’s totally unrealistic to think otherwise. The analysis activities to prepare the business case are incomplete until an initial risk assessment is performed. Project risk is defined as an uncertain event or condition which has impact at least on time, cost, scope or quality. Risk analysis includes the following processes:

  • Risk Identification
  • Risk Assessment
  • Risk Response Planning
  • Organizational Readiness Assessment
  • Risk Avoidance
  • Risk Rating

Risk Identification: The cause of risk should be described with its impact. The goal is to identify business, financial, technical and operational risks. The first thing we must do in risk identification is to recognize the areas of the project where the risks can occur. It basically includes scope of the project, cost and schedule decided for the project, change in customer requirements and resource management.

Continue reading