) and project specifics, a common sequence starts with a
1. Project Vision Document: This document outlines the overall goals,
objectives, and scope of the project, providing a high-level overview for
all stakeholders.
2. Business Analysis Plan: This plan details the approach, scope,
deliverables, and timeline for the business analysis activities
throughout the project.
3. Business Requirements Document (BRD): The BRD defines the
business needs and objectives that the project aims to fulfill, providing
a high-level overview of the project's requirements.
4. Stakeholder Analysis: This document identifies and categorizes
stakeholders, analyzing their influence and impact on the project.
5. Functional Requirements Document (FRD) / Functional
Specification Document (FSD): The FRD specifies how the system
will function to meet the business requirements, detailing specific
functionalities and behaviors.
6. System Requirements Specification (SRS): The SRS document
details the technical requirements that the system must meet to
support the functional requirements, often building upon the FRD.
7. User Stories (Agile): In Agile methodologies, user stories capture
specific functionalities from the end-user's perspective.
8. Use Cases: Use cases describe how users will interact with the system
to achieve specific goals, complementing user stories.
9. Requirement Traceability Matrix (RTM): The RTM links
requirements to design, development, and testing activities, ensuring
all requirements are addressed throughout the project lifecycle.
10. Process Flow Diagrams: Visual representations of how
processes will work, aiding in understanding workflows and identifying
potential issues.
11. Solution Approach Document: This document outlines the
proposed solution and how it will be implemented to meet the
identified requirements.
12. Impact Analysis Document: This document assesses the
potential impact of the project on existing systems, processes, and
stakeholders.
13. Change Request Documents: These documents are used to
manage and track any changes or modifications to the project
requirements or scope.
14. Test Plan/Test Cases: These documents outline the testing
strategy and specific test cases to ensure the system meets the
defined requirements.
15. Minutes of the Meeting/Status Reports: These documents
capture the key discussions, decisions, and progress updates
throughout the project.
2. How do you see yourself fit for the role of business analyst in our
company?
Secondly, illustrate your experience, attitude, and skills that make you a
good fit for the company.
You can give examples of the previous works that show the interviewer what
benefits you will bring to the company. Make sure your answer has a
problem and the solution you implemented.
Pro Tip: Make sure you also focus on the skills outlined in the job
advertisement when you are highlighting and explaining your experience
and competencies.
1. Started off as a Programmer analyst in Cognizant where my role was to
revise the functional requirements collected by the Business Analyst. So, I
found myself interested in the role and stepped up by participating in the
elicitation meetings and providing demos to the clients.
2. Further, in REI Systems, along with the full-fledge responsibility of BA, I
also worked as a Scrum Master as at that time our entire project was under
transition to Agile Scrum methodology. So I gained a good experience of it as
I got to understand the practical advantages of Agile over waterfall and was
handling the entire project by acting both as a BA and SM.
3. Now currently in SATECH, being a senior business analyst:
a. I am working as a Product Owner to our current project.
b. Here I have to be in constant touch with our Business stakeholders and
maintain an updated epic consisting of all the current and upcoming User
Stories.
c. Keep in touch with UI/UX team to align the in-hand requirements with in
progress wireframes.
d. I also have to keep a check on all the US maintained by the Associate
BAs and the take regular updates on the ongoing work in the current sprint.
e. In case, there is any [ADC1]
Senior Business Analyst professional with 9.5 work experience.
Roles and Responsibilities
• Elicit & Translate Business requirement to User Stories\BRD\FRD\
SRS
• Conduct Gap Analysis\Scope Analysis\Impact Analysis on Business
Process using techniques like use case diagrams (UML) \ Context
Diagram (Data Flow Modelling) \ BPMN (process modelling)\Flow
charts
• Conduct AS-IS and TO-BE Analysis and suggest Fit for Business
Solution ) and project specifics, a common sequence starts with a
1. Project Vision Document: This document outlines the overall goals,
objectives, and scope of the project, providing a high-level overview for
all stakeholders.
2. Business Analysis Plan: This plan details the approach, scope,
deliverables, and timeline for the business analysis activities
throughout the project.
3. Business Requirements Document (BRD): The BRD defines the
business needs and objectives that the project aims to fulfill, providing
a high-level overview of the project's requirements.
4. Stakeholder Analysis: This document identifies and categorizes
stakeholders, analyzing their influence and impact on the project.
5. Functional Requirements Document (FRD) / Functional
Specification Document (FSD): The FRD specifies how the system
will function to meet the business requirements, detailing specific
functionalities and behaviors.
6. System Requirements Specification (SRS): The SRS document
details the technical requirements that the system must meet to
support the functional requirements, often building upon the FRD.
7. User Stories (Agile): In Agile methodologies, user stories capture
specific functionalities from the end-user's perspective.
8. Use Cases: Use cases describe how users will interact with the system
to achieve specific goals, complementing user stories.
9. Requirement Traceability Matrix (RTM): The RTM links
requirements to design, development, and testing activities, ensuring
all requirements are addressed throughout the project lifecycle.
10. Process Flow Diagrams: Visual representations of how
processes will work, aiding in understanding workflows and identifying
potential issues.
11. Solution Approach Document: This document outlines the
proposed solution and how it will be implemented to meet the
identified requirements.
12. Impact Analysis Document: This document assesses the
potential impact of the project on existing systems, processes, and
stakeholders.
13. Change Request Documents: These documents are used to
manage and track any changes or modifications to the project
requirements or scope.
14. Test Plan/Test Cases: These documents outline the testing
strategy and specific test cases to ensure the system meets the
defined requirements.
15. Minutes of the Meeting/Status Reports: These documents
capture the key discussions, decisions, and progress updates
throughout the project.
2. How do you see yourself fit for the role of business analyst in our
company?
Secondly, illustrate your experience, attitude, and skills that make you a
good fit for the company.
You can give examples of the previous works that show the interviewer what
benefits you will bring to the company. Make sure your answer has a
problem and the solution you implemented.
Pro Tip: Make sure you also focus on the skills outlined in the job
advertisement when you are highlighting and explaining your experience
and competencies.
1. Started off as a Programmer analyst in Cognizant where my role was to
revise the functional requirements collected by the Business Analyst. So, I
found myself interested in the role and stepped up by participating in the
elicitation meetings and providing demos to the clients.
2. Further, in REI Systems, along with the full-fledge responsibility of BA, I
also worked as a Scrum Master as at that time our entire project was under
transition to Agile Scrum methodology. So I gained a good experience of it as
I got to understand the practical advantages of Agile over waterfall and was
handling the entire project by acting both as a BA and SM.
3. Now currently in SATECH, being a senior business analyst:
a. I am working as a Product Owner to our current project.
b. Here I have to be in constant touch with our Business stakeholders and
maintain an updated epic consisting of all the current and upcoming User
Stories.
c. Keep in touch with UI/UX team to align the in-hand requirements with in
progress wireframes.
d. I also have to keep a check on all the US maintained by the Associate
BAs and the take regular updates on the ongoing work in the current sprint.
e. In case, there is any [ADC1]
Senior Business Analyst professional with 9.5 work experience.
Roles and Responsibilities
• Elicit & Translate Business requirement to User Stories\BRD\FRD\
SRS
• Conduct Gap Analysis\Scope Analysis\Impact Analysis on Business
Process using techniques like use case diagrams (UML) \ Context
Diagram (Data Flow Modelling) \ BPMN (process modelling)\Flow
charts
• Conduct AS-IS and TO-BE Analysis and suggest Fit for Business
Solution DETAILED NOTES: BUSINESS ANALYSIS TECHNIQUES FOR
COMPLEX IT PROJECTS (NON-E-COMMERCE)
1. ENTERPRISE ANALYSIS / PRE-INITIATION STAGE
Objective: Understand high-level business needs and strategic goals. Define
potential project opportunities.
Key Techniques & Deliverables: - SWOT Analysis: Identifies strengths,
weaknesses, opportunities, and threats. Helps assess internal and external
factors. - Feasibility Study: Evaluates viability, cost, and risks of a
proposed solution. - Business Case Development: Justifies investment
using ROI, risk mitigation, and operational value. - PESTLE Analysis:
Understands macro-environmental factors (Political, Economic, Social,
Technological, Legal, Environmental).
Real-Time Project (Banking Sector): - Project: Modernizing a core
banking system. - Trigger: Rising operational costs and customer
dissatisfaction. - BA Tasks: Conducted competitor analysis, regulatory impact
review, and aligned modernization with enterprise strategy.
2. INITIATION / PLANNING STAGE
Objective: Define the scope of the project, identify stakeholders, and
establish governance.
Key Techniques & Deliverables: - Stakeholder Analysis: Use
Power/Interest Grid to classify stakeholders. - RACI Matrix: Clarifies roles
and responsibilities (Responsible, Accountable, Consulted, Informed). -
Requirement Management Plan: Outlines how requirements will be
gathered, documented, tracked. - Project Charter & Scope Statement:
Includes business needs, key deliverables, assumptions.
Real-Time Project (Healthcare IT): - Project: Development of a
centralized Electronic Health Record (EHR) system. - BA Tasks: Identified
internal stakeholders (clinicians, IT, compliance) and external ones
(insurance bodies). Defined scope boundaries to avoid data privacy risks.
3. ELICITATION & REQUIREMENTS GATHERING
Objective: Gather clear, complete, and agreed-upon requirements from all
stakeholders.
Key Techniques & Deliverables: - Interviews: With subject matter
experts (SMEs). - Workshops & Focus Groups: Used for collaborative
refinement of needs. - Use Cases & User Stories: Define system
interaction from end-user perspective. - Document Analysis: Review
existing SOPs, regulatory guidelines. - Observation/Shadowing:
Understand current workflow limitations.
Real-Time Project (Telecommunications): - Project: Upgrade of call
center infrastructure. - BA Tasks: Interviewed call agents, analyzed complaint
logs, observed call handling during peak hours. Captured functional needs
(auto-ticket creation, call routing) and non-functional needs (response time,
availability).
4. REQUIREMENTS ANALYSIS & DOCUMENTATION
Objective: Refine, prioritize, and document requirements in a structured
format.
Key Techniques & Deliverables: - MoSCoW Prioritization: Must have,
Should have, Could have, Won’t have. - Process Modeling (BPMN):
Visualizes workflows. - Data Flow Diagrams (DFD): Maps data movement.
- Entity Relationship Diagrams (ERD): Defines database relationships. -
Gap Analysis: Compare current vs future state.
Real-Time Project (Public Sector - Tax Administration): - Project:
Digital transformation of tax filing system. - BA Tasks: Modeled current
manual filing process, identified redundancies. Created TO-BE models for
online submission and real-time validation. Documented regulatory
compliance requirements.
5. SOLUTION ASSESSMENT & VALIDATION
Objective: Ensure the developed solution satisfies all requirements and
delivers value.
Key Techniques & Deliverables: - Requirements Traceability Matrix
(RTM): Ensures each requirement is met. - Test Case Design & Mapping:
BAs validate UAT scenarios. - Defect Triage Meetings: Prioritize issues
based on business impact. - Usability Testing: Checks for ease of use. -
Pilot Testing / Dry Runs: Validate the system in a controlled environment.
Real-Time Project (Logistics & Supply Chain): - Project: Implementation
of a warehouse automation system. - BA Tasks: Created traceability matrix
for all inventory movement features. Conducted UAT with warehouse staff.
Participated in daily stand-ups during defect triage.
6. IMPLEMENTATION & CHANGE MANAGEMENT
Objective: Support smooth transition to the new system and drive user
adoption.
Key Techniques & Deliverables: - Change Impact Assessment:
Identifies affected departments/processes. - Training Needs Analysis &
Materials: Instructor guides, video demos. - Communication Plans:
Timely updates, newsletters, executive emails. - Readiness Assessment:
Measures preparedness. - Hypercare Support: Post-implementation issue
handling.
Real-Time Project (Pharmaceutical Manufacturing): - Project: Rollout of
an automated compliance and quality tracking system. - BA Tasks:
Developed change impact matrix. Collaborated with training teams. Provided
on-site support during go-live week. Monitored adoption through KPIs.
7. CONTINUOUS IMPROVEMENT / POST-IMPLEMENTATION
Objective: Ensure sustained value and gather lessons learned for future
projects.
Key Techniques & Deliverables: - Lessons Learned Workshops - Post-
Implementation Review (PIR) - KPI Tracking / Dashboards - Service
Requests & Enhancements Management
Real-Time Project (Energy Sector): - Project: Smart meter data analytics
dashboard. - BA Tasks: Reviewed dashboard adoption metrics. Suggested
enhancements based on user feedback. Facilitated PIR to evaluate what
went well and what to improve.
Essential BA Tools by Stage: | Stage | Tools | |——-|——-| | Planning | MS
Project, Confluence, Trello | | Elicitation | Miro, Figma, Visio, Zoom | |
Documentation | Word, Excel, Balsamiq, Draw.io | | Testing | JIRA, Zephyr,
TestRail | | Change Mgmt | Notion, SharePoint, Google Slides |
Would you like a simplified one-page version or a downloadable PDF version
of this document?
