A Self-made Handbook created by me for the new Business Analysts for faster learning of Business Analysis

1. AUTHOR: DEEPRAJ PATHAK
PLACE: PUNE
DATE: 16.09.2019
Business
Analyzopedia

2. Business Analysis is a research discipline of identifying Business needs &
determining solutions to Business problems.
Solutions often include a Software Systems Development component but
may also consist of –
 Process Improvement
 Organizational Change
 Strategic Planning
 Policy Development
What is Business Analysis?

3.  Business Analysis is a need, not a luxury.
 Software Developers think in a confined way – it’s due to their nature of job,
not like they can’t think out-of-the-box.
 To design any system, an Holistic 360 degree view is required to be visualized
first.
 Trained BAs(Business Analysts) know to provoke customers by mind teasers
to get the exact answers related to the system.
 Software Industry runs on 80:20 rule i.e. System Designing gets 80%
weightage & Software Development gets 20% weightage. It implies that if you
design a system well in advance then Developers are more relaxed.
Why Business Analysis?

4. Software Development Life Cycle

5. Difference between Agile & Waterfall

6.  Requirement Gathering(BA Questionnaire, BA Checklist, User Story,
Prototyping, Wireframing)
 Requirement Analysis & Feasibility Study
 Scoping(MoSCoW, Story Prioritization)
 Software Designing(BRD, FRD, Usecase Diagrams, RTM)
 Impact Analysis
 Effort Estimation(FPA, TPT, PERT, UCP, CoCoMo, Planning Poker)
 Costing
 Pricing
 Customer Communication
 Create Functional Testcases, referring Functional Requirements &
Acceptance Criteria
 Drive UAT
Business Analysis R&R

7.  Communicate with Contacts
 Connect People
 Create Reports
 Enable Visitors to create information
 Fulfil Orders
 Manage Customer Information
 Manage Information
 Manage Resources
 Manage Users & Permissions
 Manage Workflow
 Market an Offer
 Partner with External Organizations
 Present Information
 Process Payment
 Purchase Products or Services
 Respond to Disruptions in Service
 Search for Information
 Support Customers
Requirement Gathering(Generic BA Checklist)

8. Science: Why? How?
Arts: What? Who? When? Where?
Requirement Gathering(BA Questionnaire)

9. User Story:-
As A <Type of User>
I Want to perform <Some Action>
So that, I can achieve <Some Goal>
Acceptance Criteria:-
Given <Some Condition>
When I perform <Some Action>
I should get <Some Desired Result>
Requirement Gathering(User Story)

10. Wireframe:- a low-fidelity static way to present a product, can efficiently outline
structures & layouts. Wireframe is a basic Visual representation of Design. It has got
nothing to do with functionalities.
Mockup:- a high-fidelity static way to present a product, should demonstrate
information frames & statically present content & functions. Unlike a wireframe, a
mockup looks more like a finished product(Only from Look perspective).
Prototype:- is already very closed to a finished product. Here, processes can be
simulated & user interaction can be tested. Early Prototyping can save a lot of
Development costs & time so that the work of Backend Product Architecture will not
be in vain because of unreasonable User Interface Design.
Tools available in market: Balsamiq, Sketch, Photoshop, Adobe illustrator etc.
A Prototype is an excellent tool to obtain user feedback & to test the Product.
Requirement Gathering(Wireframe, Mockup &
Prototype)

11.  Business Problem Statement
 Current Business Process
 Scope Statement
 Key Business Objectives
 Project Completion Criteria
 Risks & Limitations
 Assumptions
 Functional & Non-Functional Requirements
 Cost & Scheduling Parameters
 New/Modified Business Process
 Training
 Stakeholders List
 Quality Measures
 Checklists(Process & Requirements)
Software Designing(BRD)

12.  Introduction
a. Purpose
b. Scope
c. Background
d. References
e. Assumptions
f. Constraints
g. Document Review
 Methodology
 Functional Requirements
a. Context
b. User Story/Functionalities
c. Use-case Diagrams
d. Logical Data Model/Data Dictionary
 Non-Functional Requirements
a. Interface Requirements
b. Hardware/Software Requirements
 Glossary
Software Designing(FRD)

13. Sample Requirement Traceability Matrix

14. Questions?

15. Thanks 