Documentation is a vital part of the business processes. This gives the clarity of the project and defines its depth, functionality, requirements and many more details in a descriptive manner. A business analyst have to prepare these kinds of documentation as and when required in project life cycle.
Though a business analyst has to prepare different business documents from time to time, the templates can vary organization to organization. The list of documents also depends on the domain, business analysis approach, the complexity of the project, and project life cycle model, etc.
At BA centric we provide proper guidance for creating such templates and documentation. Here we will see the list of documents that are required commonly across the domains.
- Business Case
- Business analysis plan
- Business Requirement Document
- Use Case Documents
- User Stories
- Stakeholder Management plan
- System requirement specification plan.
- 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
While preparing these documentation business analyst has to co-ordinate with the respective project managers, stakeholders, and implementation team if needed. At every stage, there are review meetings that help to analyze the process more practical and the documentation can be updated as and when required.
At every phase, the business analyst needs to check out whether the project is going as per plan and the deliverables are ready by the mentioned time frames. This is a very usual practice which is followed by almost all types of industries.