Which are the documents prepared by a Business Analyst?

In this blog, we are going to examine – Which are the documents prepared by a Business Analyst? Business analysts may prepare or be part of several documents in a project life cycle.

The documents, which a business analyst prepares, depend on the business analysis approach, complexity and size of the project and organizational standards. For example, the number of documents created for a project using the Agile Methodology will have considerably less number of documents as compared to the Waterfall Methodology.

1) So, which are the documents prepared by a Business Analyst in different methodologies?

1. There are a number of documents, which can be created by a business analyst. Here is a comprehensive list of such documents(please note that a business analyst may not create all the documents in every project):

  • Business Case
  • Business Analysis Plan
  • Business Requirements Document (BRD)
  • Stakeholder Management Plan
  • System Requirements Specification Document (SRS)
  • Functional/Process Document
  • Gap Analysis Document
  • Solution Approach Document
  • Requirements Traceability Table (RTT)
  • Change Request Logs
  • Impact Analysis Document
  • System Test Plan
  • System Test Cases
  • UAT Progress Report

2. It is pertinent to list down the documents prepared by a business analyst (We are also including the Product Owner) in projects following Agile Methodologies separately:

  • User Story Cards
  • Product Backlog
  • Sprint Backlog
  • Burn down and Burn up Charts

A brief description for each of these is provided below:

1.1  Business Case

A document describing solution options, their comparisons, and recommended solutions based on parameters relevant to the organization.

1.2  Business Analysis Plan

A plan listing all the business analysis activities, to be carried out in the project. Generally, it is part of the project plan.

1.3  Business Requirements Document

Requirements for the project (Change initiative) are described from the customer’s perspective.

1.4  Stakeholder Management Plan

Business analysts create this document to document the strategy to handle stakeholders based on the stakeholder maps.

1.5  System Requirements Specification (SRS) Document

A detailed description of functional and non-functional requirements comprising screen designs, business rules, data models, etc.

1.6  Functional/Process document

A subset of SRS documents capturing the process models or functional maps of the proposed system.

1.7  Gap Analysis Document

A document prepared in commercial off-the-shelf (COTS) product implementation projects. This document describes the gaps between the process TO-BE implemented vs the AS-IS processes.

1.8  Solution Approach Document

Again, a document more relevant for commercial off-the-shelf (COTS) product implementation projects. It describes the solution approach to address the gaps identified in the gap analysis document.

1.9  Requirements Traceability Table (RTT)

A comprehensive matrix to capture the relationship and attributes of requirements for impact analysis (in case of change requests).

1.10  Change Request Logs

A log of all the change requests in the project with the date of request, requester, etc.

1.11  Impact Analysis Document

A document capturing all the details of a change including the value, its impact, cost, effort, approval status, etc.

1.12  System Test Plan

A plan for carrying out our system testing for a project with testing strategy, case coverage, test data preparation strategy, etc.

1.13  System Test Cases

The test cases with test data are based on the system test plan.

1.14  UAT Progress Report

Business analysts coordinate the user acceptance testing phase and during the UAT phase, they submit the status report to all the stakeholders.

2) Documents created in Agile projects

The number of documents created in Agile projects is limited as mentioned above. A brief description of these documents is below:

NOTE: Some of the documents mentioned above may also be created on an as-needed basis.

2.1  User Story Cards

A format that captures the user story, details based on conversation and the acceptance test cases. Think of it like a postcard with sides. The front side contains the user story and its details. The back side contains the acceptance test cases.

Read Also: Writing Effective User Stories | User Story Tutorial

2.2  Product Backlog

A listing of to-be-done requirements (captured as user stories or any other format) with priority and estimation. It is maintained on the product level and not all requirements are detailed out in the phase.

You can also check out Product Backlog Mistakes To Avoid

2.3  Sprint Backlog

A subset of product backlog to-do items, which is to be taken up for development in a particular sprint. These are fully detailed out. A sprint backlog may contain:

  • Requirements
  • Defects
  • Changes etc.

2.4  Burn Down and Burn Up Charts

Charts to track the status of the requirements. These charts can be made for a sprint as well as for the entire product.


In this blog, we have discussed the documents prepared by Business Analysts using different methodologies. The specific documents created may vary depending on the project management methodology being used. For instance, traditional projects usually require documents such as project charters, requirements documents, and impact analysis documents. On the other hand, Agile projects require documents such as user story cards, product backlogs, and sprint backlogs.

If you're looking to become a skilled Business Analyst and learn how to create necessary documents that drive successful project outcomes, Techcanvass’s ECBA Certification Course is the perfect fit for you!

Our course covers essential documents prepared by a Business Analyst, including System Requirements Specification (SRS), User Story Cards etc. These skills will help you in your future career as a Business Analyst and ensure that you're able to create high-quality, effective documents. Plus, you'll have access to real-life projects that allow you to apply your learning in both Waterfall and Agile contexts.



Leave a comment

Your email address will not be published. Required fields are marked

Comment inserted Successsfully

Please login to Comment


Alternate Text


Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text

Related Blogs

 ECBA Certification

What Is ECBA Certification?


Product Owner vs Business Analyst vs Scrum Master

Product Owner vs Business Analyst vs Scrum Master


ECBA Exam Passing Score

ECBA Exam Passing Score


ECBA Exam Questions

ECBA Exam Questions



Business Analysis Body of Knowledge Guide (BABOK Guide)


Which Business Analyst Certification is Best?

Which Business Analyst Certification is Best?


Become a Business Analyst In India

How to Become a Business Analyst In India?


Become a Business Analyst Without IT Background

How To Become a Business Analyst Without IT Background?


Top 10 Challenges Faced by Business Analysts

Top 10 Challenges Faced by Business Analysts


Handle Difficult Stakeholders

How to Handle Difficult Stakeholders?


Roles & Responsibilities of A Business Analyst

What Are The Roles & Responsibilities of A Business Analyst?


    Grab offer

    Copyright © Techcanvass | All Rights Reserved