Business Analysis
Training
1
Day 1









Role of a Business Analyst
Structure of a Project Team
System Development Life Cycle (SDLC)
Importance of Requirement gathering.
Different Types of Requirements.
Requirement Gathering Techniques
JAD Session
Role of a BA in JAD Session
How to conduct JAD session?
2
Business Analysis - Elements



Business Strategy - Analyzing the strategic profile of
the company and implementing policy changes
based upon this analysis.
Business Architecture - Analysis of the actual way in
which the business functions. This includes
evaluating objectives and the resources and
processes currently in place to achieve them.
Changes to the business architecture will be made
based upon this analysis.
Business Systems - Analysis of the businesses
information systems needs, defining required
changes to information systems based upon this
analysis.
3
Business Analysis - Phases



Phase 1 - Why? - This phase is purely about fact
finding. Normally, this will involve the formulation of
a feasibility study to examine the business case put
forward for changes.
Phase 2 - Work - In this phase the business analyst
will develop a project or requirements plan, which
will need to be agreed with all stakeholders, and
then implemented.
Phase 3 - Working? - This is the final phase, where
any changes implemented need to be proven as
working. Additionally, at this phase the business
analyst needs to confirm that all requirements have
been met.
4
Project Life Cycle
Initiation
Analysis
Development
Testing
Implementation
5
Role of a Business Analyst




Business Analysts act as a liaison between Business and IT.
Business Analysts must analyze and synthesize information
provided by a large number of people who interact with the
business, such as customers, staff, IT professionals, and
executives.
The Business Analyst is responsible for eliciting the actual needs of
stakeholders, not simply their expressed desires.
In many cases, the Business Analyst will also work to facilitate
communication between organizational units.
6
Role of a BA (Initiation)



Identify critical business pain points
Pain points then be used to create a business
case which shows the problem definition and
its solution, cost of the project and ROI to the
organization
Business case will be referred through out
the project to ensure change is inline with the
expected business benefits; to ensure if the
business case is still relevant
7
Role of a BA (Analysis)




BA will work with SMEs, Business users,
defines requirements
BA will work with the dev team, Architects to
create design and define the solution
BA will create BRDs, Use cases, data
mapping etc (if required)
BA will work with QA team to ensure proper
test cases are captured per defined
requirements
8
Role of a BA (Development)


BA will work with Dev Team to clear
requirement clarifications and find out any
deviations
BA will ensure and control requirement
changes
9
Role of a BA (Testing)



BA will work with business and set defect fix
priorities
Will work with business and coordinate User
Acceptance Testing and user trainings
Disputes between the business and
development concerning what is and what is
not an off spec defect will often be resolved
by the BA using documentation created in
earlier phases
10
Role of a BA (Implementation)


BA will ensure the use of software system
after go-live
BA will work on capturing
requirements/enhancements post production
11
Systems Development Life Cycle
12
Structure of Project Team
Few samples of a project:
 Web Project
 Reporting Project
 Data Warehouse Project
 Data Migration
 Legacy Remediation and Migration
13
Requirement Gathering
Techniques



Different Techniques used for different
project
Another important factor to influence the
selection of requirement gathering technique
is knowledge of business users
Technique that was successful in one project
need not be successful for other project or
different stakeholders
14
Requirement Gathering
Techniques (Contd)

Different techniques are as follows










Brainstorming
Document Analysis
Focus Group
Interface Analysis
Interview
Observation
Prototyping
Requirements workshop (JAD)
Reverse Engineering
Survey
15
Requirement Gathering Issues








Users do not understand what they want or users don't have a
clear idea of their requirements
Users will not commit to a set of written requirements
Users insist on new requirements after the cost and schedule
have been fixed
Communication with users is slow
Users often do not participate in reviews or are incapable of
doing so
Users are technically unsophisticated
Users do not understand the development process
Users do not know about present technology
16
Joint Application Design (JAD)



Joint application design (JAD) is a process used
to collect business requirements while developing
new software system
The JAD process also includes approaches for
enhancing user participation, expediting
development, and improving the quality of
specifications
It consists of a workshop where knowledge workers
and IT specialists meet, sometimes for several days,
to define and review the business requirements for
the system.
17
JAD Session Key Participants






Executive Sponsors
Project Manager
Subject Matter Experts
Facilitator/Session Leader
Scribe
Observers
18
JAD Session - Guidelines








Use experienced and skilled facilitators
Get Executive Sponsor’s commitment and support
Get the right people to participate, predefine their
roles and responsibilities
Set clear defined, well understood and obtainable
goals or objectives
Plan detailed agenda and stick with it
Define deliverables clearly in advance
Keep Technical Jargon to a Minimum
Produce Final Document Quickly
19
Advantages of JAD




Reduced time in analysis
Improved system quality and productivity
Reduced scope creep in other words reduced
system cost
Enhanced communication and relationship
between IT and business
20
Different Requirement Types

Requirements are categorized into different
types:











Customer Requirements
Architectural Requirements
Structural Requirements
Behavioral Requirements
Business Requirements
Functional Requirements
Non-functional Requirements
Performance Requirements
Design Requirements
Derived Requirements
Allocated Requirements
21
Day 2

Compare and Contrast different SDLC Models





Waterfall
SCRUM
Rational Unified Process (RUP)
RAD methodology
Deep Dive into SCRUM




SCRUM Basics
SCRUM Team Structure
SCRUM Estimation and Tracking
SCRUM Challenges
22
Waterfall Model
23
Waterfall Model - Challenges






Unstable in the beginning
Projects painstakingly long
Sequential S/W Process
Hard to handle changes
Only one team is busy at a time
Will not work for all the projects
24
Rational Unified Process (RUP)
25
Rapid Application Devt
26