BUSINESS ANALYSIS

Submitted By
Rugved Paradkar

Business Analyst Training Institute,

Dombivli (East)
Weekday Batch

1
 INDEX
Table of Content
1 Introduction of IT companies
2 Departments of IT companies
3 Project Initiation Phase
4 Requirement Gathering
5 Software Development Life Cycle
6 SCRUM

2
 IT COMPANY Capgemini
CLIENT TYPES Wipro
Infosys
Accenture
TCS
C B
2018 2021
Customer Business
Hospital A Hospital B
1) Application Development
Customer 1 (Orthopaedic) (Orthopaedic)
 BFSI - ICICI Project Types 1.1 Software Development
Customer 2  Capital Market - Angle Broking (B2B) 1.2 Mobile Application ?
Customer 3  Investment Banking - J P Morgan Mobile App

Development
. E Commerce - Flipkart
 Automobile - Tata Motors 1.3 Website & Web Application
.
 Manufacture - Menon Piston Development
.  Healthcare - Zicus Tech 2) Customization
.  Pharma -
Mahindra 2.1 Add New Feature /
.  FMCG - Hindustan Unilever
 Travel & Hospital - Yatra (BA) Functionality
..
 Education - Universities 2.2 Remove Existing Feature/
.
 Aviation - Airlines TCS Functionality
 Real Estate - Lodha 2.3 Change Existing Feature/
Consultant (BA) ICICI
 Government
Functionality
(Client)
Flipkart 3) Services
(BA) 3.1 Maintenance and Support
- AMC
BA Multitasking Role 3.2 Development and Testing Infosys Cognizant
3.3 Consulting (Development) (Testing)
Global/ Universal Business Specific 3.4 Migration )
Product Product Development

Development Need BAs on B2B Project where BA

will be allocated on
I) Multiple clients in same domain
CX.
less % BAs Hired
Project 1: ICICI Bank
in Project 2: Yes Bank
B2C Projects. Project 3: IIDFC Bank
ii Multiple clients in different domain
ex.
Project 1: ICICI Bank
3
Project 2 : Flipkart
Project 3 : Tata Motors
Department of IT company
1. Business Team/ Management Team
2. Marketing/Sales/Pre-Sales
3. Account / Finance
4. System/Network
5. Project management

4
 Project manager

Development Testing Database Support Business

team team Team Team analyst

Team Quality Database Support

Leader Assurance Administrator Administrator

Developer Developer Developer Tester Tester Tester Database Database Database Support Support Support
Developer Developer Developer Executive Executive Executive

5
 Initial Approach of IT & Client

ABC Tech 1) Online / Offline Marketing done by ABC Easy Car Rental
(IT) 2) Sales of ABC will find ECR online or through their (ECR)
database
 Client
Business
3) Through Reference
 Accounts
• ECR will get to know about ABC through their reference  Sales and Marketing
• ABC will get to know about ECR through their reference  Reception /
4) ECR will publish tender online / offline Customer Support
 Driver
 Car Maintenance

6
 GAP Analysis
IT Sales will
Client will convey
Product Features IT Will Suggest understand existing
missing features
business of client
A F K O
B G L P
C H M Q
D I N R
E J S

7
 Project Initiation Phase
ABC Tech (IT) Easy Car Rental (Client)

1 Company Portfolio & Product Demo

4 Feasibility Check 3 Meeting overview
PSD 2 Gap analysis
PSD 6 (Project scope document)
PSD
5 (Project Scope Document) 7 (Project Scope Document)

Project Business
Request POC Sales/ PSD Sign off.
9 (Proof of concept) Business
Manager Team Presales 8 (Project Scope Document)
POC
12 (Proof of concept)
POC Team
13 (Proof of concept)
16 Request for costing 15 Request for costing POC Sign off.
SOW 14 (Proof of concept)
SOW & SLA
17 (Scope of work) 19 (Statement/ scope of work) SOW & SLA
(Service level agreement) 20 (Scope of work)
(Service level agreement)
(Service level agreement) 18

SOW & SLA Sign off.

21 (Scope of work)
(Proof of concept) 10

(Proof of concept) 11

(Service level agreement)

Request POC
SLA

POC

SLA – Service level agreement

 Payment terms, currency rate, due dates of
payment
 Free support period
 Technology and framework
SOW – Statement/ Scope of work  Software development method
UI Designer Team
Legal Team  Modules, features tasks AMC  Product licencing terms
Or
 No of resources allocated.  Hardware configurations, software licences, server
Business analyst
 Timeline configuration purchased by client. 8
 Cost  Changes will be charged extra on actual.
 Non-disclosure agreement
 Project planning & Resource Allocation

ABC Technology Easy Car Rental

(IT Company) (Client Company)

 Business Team will allocate

Project manager.
 Project Manager will allocate
Project team.
 Business Analyst will get the
product training.
 Project kick-off meeting

PROJECT MANAGER WILL INTRODUCE HIS TEAM TO CLIENT

PROJECT TEAM CLIENT TEAM

CLIENT WILL INTRODUCE HIS TEAM TO PROJECT MANAGER

9
 RACI Matrix
Sr. Time
Department Name POC Designation Mobile no Email RACI
No zone
1 Business Rahul Head 9234567898 [email protected] AST R
2 Business Aniket Head 8981234567 [email protected] EST A
Sr.
3 Business Vishal 8561237898 [email protected] CST C
Associate
Business Sr.
4 Gopal 6781234598 [email protected] MST I
Operation Associate

R - Responsible (POC who is responsible to give requirement)

A - Accountable (POC who approve / sign off requirement)
C - Consultable (POC to whom team should consult)
I - Informable (POC who is getting impacted)

10
 REQUIREMENT GATHERING
Client's Existing Business Solution To Be Delivered
(business team of client)

AS-IS Business Process TO-BE Business Process

REQUIREMENT

1 2
GATHERING
HIGH LEVEL

A B C D E P Q R S T BRD/
HLD

3 4
REQUIREMENT

P1 Q1 SRS/
GATHERING
LOW LEVEL

(SMEs)

SME SME P2 Q2 FRS/

P3 Q3 TD/
P4 Q4 LLD
. .

11
 HIGH LEVEL DOCUMENT
IT Business Analyst Client-Business Team
Business Requirements on high level Client's

Arrange Meeting with Client's Business Team as per RACI Matrix to discuss Client's
1 Existing Business process on high level
Business Requirement Document /High Level Document

(AS-IS Business Process)

(Main Business Process/Happy Flow/High level Business Process)

Existing Business

2 Attend Meetings
3 Send Minutes of Meeting
Approve/Rectify Minutes of
4
Meeting
5 Send Diagram of High-Level Existing Business Process
6 Approve/Rectify Diagram
BRD/HLD

7 Arrange Meeting to Discuss High Level Flow of Solution / Happy Flow

8 Attend Meeting
Technical Requirements on high level

9 Send Minutes of Meeting

(TO-BE Business Process)
Client's Existing Business

Approve / Rectify Minutes of

10
Meeting
11 Send Diagram of High-Level Flow of Solution / Happy Flow
12 Approve / Rectify Diagram
13 Prepare UI Screens / Prototypes on High Level
14 Approve / Rectify UI Screens
15 Send BRD / HLD
16 BRD / HLD signoff

12
 LOW LEVEL DOCUMENT
IT Business Analyst Client-Business Team
level/Detail Level/Department level.
Business Requirements on Low

Arrange Meeting with Client's Business Team as per RACI Matrix to discuss Client's Existing Business
Clients Existing Business
(AS-IS Business Process)

1
process on Low level/Detail Level/Department Level.
2 Attend Meetings
SRS/FS/FRS/UCS/LLD/TD/FRD/FD

3 Send Minutes of Meeting

4 Approve/Rectify Minutes of Meeting
5 Send Diagram of Low level/Detail Level/Department Level Existing Business Process
6 Approve/Rectify Diagram
Technical Requirements on Low level/Detail

7 Arrange Meeting to Discuss Low level/Detail Level/Department Level Flow of Solution

Level/Department Level. Solution To Be

8 Attend Meeting
Developed by IT Company.
(TO-BE Business Process)

9 Send Minutes of Meeting

Approve / Rectify Minutes of
10
Meeting
11 Send Diagram of Low level/Detail Level/Department Level Flow of Solution
12 Approve / Rectify Diagram
13 Send Technical Document (SRS/FS/FRS/UCS/LLD/TD/FRD/FD)

14 Technical Document Signoff

13
SRS - Software Requirement Specifications
FS - Functional Specifications
FRS - Functional Requirement Specifications
UCS - Use Case Specifications
LLD - Low Level Document
TD - Technical Document
FRD - Functional Requirement Document
FD - Functional Document

14
 ABC Client
Software Development Life Cycle

Version Build
Development V1.0 Testing V1.19
User Acceptance Go-Live/ Production Maintenance &
Testing (ECR) Support
Internal Deployment UAT Deployment Release
V1.2 (ECR)
V1.20 V1.39 AMC
Production Deployment
V1.19 V1.21
UAT Production
Development Testing
Server Server
server Server
Unit/white Box/Integration testing
Done by developers. Functional / Black Box / Regression
Functional testing done Product used by end users.
/ Integration Testing
Jan 21 V1.0 -> Registration + Login by client users
Done by testing team & BA
V1.0 V1.19 Final Product V1.39
(Registration + Login +) V1.0
My Account Bug1 Issue 1
Defect1
+ Forgot password Bug2 Issue 2
Defect2
+ Bug1 (V1.0) Bug3 Issue 3
Defect3
+ Bug2 (V1.0) V1.1 Issue 4
Defect4
Bug1
Defect5
V1.1 -> Bug3 (V1.0) Bug2
Defect6
Bug1 (V1.1) Bug3
Defect7
Bug2 (v1.1) Bug4
Bug3 (V1.1) V1.2
Bug4 (V1.1)
Jan 27 V1.19 Final Application
Sign off
V1.19
V1.20 -> Defect1
Defect2
Defect3
V1.20
V1.20 15
V1.39
 Initiation
Planning &
Maintenance Resource
& Support Allocation

Software
Live/ Development Requirement
Production Life Cycle Gathering
Phases

UAT Development

Testing
16
 SCRUM All Requirements
Product Backlog
Convert Requirements
into User Stories and User Story 1
Requirement Gathering Product Owner User Story 2
Create Product Backlog
User Story 3
Client User Story 4
User Story 5
Business Analyst .
.
Convey priority user stories .
to Scrum Master and Cross
Functional Teams by
Creating Sprint Backlog

Scrum Master

Cross Functional Teams

(Developer, Tester)

Cross Functional teams will start

developing features / users’ stories
according to sprint backlog.

17
 Sprint 0 Sprint 1 Sprint 2 Sprint 3 Sprint n

15 to 30 Days Duration 15 to 30 Days Duration 15 to 30 Days Duration 15 to 30 Days Duration 15 to 30 Days Duration
(1st Jan - 20th Jan) (21st Jan - 9th Feb) (10th Feb - 29th Feb) (1st Mar - 20th Mar) (21st Mar - 9th Apr)

Sprint Backlog 1 Sprint Backlog 2 Sprint Backlog 3

➤User Story 1: ➤ User Story 2: ➤User Story 4:
As a register user I can As a register user I can As a register user I can update
attach contact attach files my status
➤User Story 3: ➤Bug 1 of Sprint Backlog 1
As a register user I can ➤Bug 2 of Sprint Backlog 1
attach photos

1 PLAN 1 PLAN 1 PLAN

5 DEPLOY 2 DESIGN 5 DEPLOY 2 DESIGN 5 DEPLOY 2 DESIGN

Iteration 3
Iteration 1 Iteration 2

3 3 3
4 TEST 4 TEST 4 TEST
DEVELOP DEVELOP DEVELOP

IT TEAM Take Requirement of SB 1 1) Take Requirement of SB 2: 1) Take Requirement of SB 3 …............. ….............

2) Deliver SB 1 2) Deliver SB 2
CLIENT TEAM Give Requirement of SB 1 Give Requirement of SB 2 1) Give Requirement of SB 3 ….............
2) Test SB 1 ….............

18