Introduction

Training for

Business Analyst
Quality Analyst
Scrum Master
Product Owner

Name : Sam Mathew

Mobile: +1240-764-4952
Whatsapp: +91 6290085382
Email: sam@globalsyst.com
Classification: Restricted Page
 Agenda
Introduction to Business Analysis
• Business Process – What and Why?
• What is a Project?
• Who is a Project Manager?
• Who is a Business Analyst?
• What is Business Analysis and why is it important?
• Roles, Responsibilities and necessary Skills for a Business Analyst
Introduction to SDLC
• Requirement Analysis
• Design Phase
• Development Phase
• Testing Phase
•Release & Maintenance
Current Trends in BA

Classification: Restricted Page 2

 What is a Business Process?
• It is a set of related tasks, performed to accomplish a specific organizational
goal. It can also be defined as a series of logically structured activities that
produce a specific service or product for customers.

Classification: Restricted Page 3

 Why do we need a Business Process?
• To become and remain
successful and
competitive, businesses
must continuously improve
their processes.
• Failure to do so is likely to
result in higher costs,
lower revenues, less
motivated employees and
fewer satisfied customers.

Classification: Restricted Page 4

 Need for Automating the Business Processes?
• Automation is moving the needle of business efficiency and simplifying
human lives in general.
• Businesses that have automated their processes cut price, save time,
and
employ their manual workforce to solve more intelligent problems.
• They let machines do the rote tasks, while eliminating the chances of
human errors.

Classification: Restricted Page 5

 Benefits of Automation
Streamline Communication

Enforce Accountability

Classification: Restricted Page 6

 Benefits of Automation
Minimize Costs and Manual Errors

Keep a Tab on your Business Processes

Classification: Restricted Page 7

 How do you Automate Business Processes?

Classification: Restricted Page 8

 Industry Based on Function
• Product Based Company – Building their own product and selling it in
market

• Service Based Company – Building product, application or part of them, for

other companies and their clients

Classification: Restricted Page 9

 What is a “Project”?

What is a “Project” ?

Classification: Restricted Page 10

 Project
• A Project is a temporary endeavor undertaken to create unique product,
service, or result.
• The temporary nature of project indicates a definite beginning and end.

Project Types:

• Fixed Bid Projects

• Billing Projects

Classification: Restricted Page 11

 IT Project Structure
Business Stakeholders

Subject Matter Experts (SMEs)

Technology Head

Technical Architect Project Manager QA Manager Production

Support

Junior Technical Technical Lead QA Leads

Architects/
Assistants
Developer QA Analysis

Classification: Restricted Page 12

 Pre-Project Activity
• Client realizes his need for a software
application.
• He will do an initial analysis on the required
features of the Software Application and will
prepare Requirements Document.

Request for Proposal (RFP)

Request for Quotation (RFQ)
RFP is a document in
which Business Statement of Work (SOW)
need appear. A request for quotation
(RFQ) is a standard
Request for Information business process whose A document that defines
(RFI) is a form that is purpose is to invite project-specific activities,
attached to RFP suppliers into a bidding deliverables, and
process to bid on specific timelines for a vendor
products or services providing services to the
client.

Classification: Restricted Page 13

 Reason for Project Initiation
• Projects plays essential role in Growth and Survival of Organization in
today’s rapidly changing competitive business environment and also in
managing the change and achieving the strategies of the enterprise.
• All projects are aimed to help the project sponsor in one way or the other
to reduce cost, increase revenue or increase efficiency or ensure
transparency etc.
• Projects may be initiated in response to a business strategy in order to,
• Cater market demand
• Tackle competition
• Increase market share
• Comply with regulation
• Create a competitive edge
• Exploit emerging opportunity and many other

Classification: Restricted Page 14

 What is Business Analysis?
• Business Analysis is the set of tasks, knowledge, and techniques required to
identify business needs and determine solutions to business problems.

Solutions often includes :

• Systems development component

• Process improvement
• Organizational change

Classification: Restricted Page 15

 Why is Business Analysis important?
• Business analysis helps stakeholders achieve a shared understanding of
the organization’s needs.
• This shared understanding puts the team in a position to make legitimate
recommendations for those needs, and ultimately puts the organization in
a position to move forward with the set of recommendations that best
meets those needs.

Classification: Restricted Page 16

 Who is a Business Analyst?
Business Stakeholders

Business Analyst Subject Matter Experts (SMEs)

Technology Head

Technical Architect Project Manager QA Manager Production

Support

Junior Technical Technical Lead QA Leads

Architects/
Assistants
Developer QA Analysis

Classification: Restricted Page 17

 Role of a Business Analyst
• A Business Analyst works as a liaison among stakeholders in order to elicit,
analyze, communicate and validate requirements for changes to business
processes, policies and information systems.

• The Business Analyst understands business problems and opportunities in

the context of the requirements and recommends solutions that enable the
organization to achieve its goals.

• A Business Analyst is responsible for ensuring the project’s outputs meet

the requirements of the business and that they are fit for purpose.

Classification: Restricted Page 18

 What are the Responsibilities of a Business Analyst?

Classification: Restricted Page 19

 Essential Skills of a Business Analyst

Classification: Restricted Page 20

 Knowledge areas of BA

Classification: Restricted Page 21

 Project Life Cycle Methodology
1 Project 2 Project 3 Project 4 Project
Initiatio Planning Execut ion Closure
n
1. Define Scope 1.Define and record 1. Execute tasks defines in 1. Obtain final acceptance
2. Hire Team requirements, constraints, the project plan for the project
3. Develop Business and assumptions 2.Implement the 2.Obtain financial, legal,
Case 2.Identify project team procurement of project and administ rative closure
and define rolesand resources 3. Release project resources
responsibilities 3.Manage resource 4.Document and
3.Create the Work allocation communicate lessons
Breakdown Schedule (WBS) 4. Implement learned
4.Develop change approved 5.Create and dist ribute
management plan changes final project report
5. Identify risks 5. Measure project 6. Archive and retain
and performance project records
define risk 6.Verify and manage 7.Measure customer
strategies change to the project satisfaction
6. Obtain plan app 7. Ensuretoproject
conform quality standards
roval deliverable
8. Monitor all risks

Montoring and Control

Classification: Restricted Page 22

 Role of a BA & PM

PM:
A Project Manager is ultimately responsible for ensuring the objectives of a
project are met and that the outputs are delivered on time, to cost and to
quality.

BA:
A Business Analyst is responsible for ensuring the project’s outputs meet the
requirements of the business and that they are fit for purpose.

Classification: Restricted Page 23

 Knowledge Areas
BA PM
• Enterprise Analysis Integration
• Planning & Management Scope Management
• Requirements Elicitation Time Management
• Requirements Analysis & Cost Management
Documentation
• Requirements Communication Human Resource Management
• Requirements Implementation Communication Management
Quality Management
Risk Management
Procurement

Classification: Restricted Page 24

 Skillset Comparison

Classification: Restricted Page 25

 Skillset Comparison

Classification: Restricted Page 26

 How do a PM and BA work together?
The Execution of a Project

Initiation Requirements Design & Construction Closure

Implementation
QA Implementation
Planning

• Scope • Planning • Execution & Control • PIR

• Budget
• Team

PM

• Scope • Document • Design • Test • Test • System • PIR

Requirements • Testing & Case • UAT Checkout
Training Creation • Train
Strategies
BA

Classification: Restricted Page 27

 SDLC
Software Development
Life Cycle

Classification: Restricted Page

 Software Development Life Cycle
• SDLC is a framework defining tasks performed at each step in the software
development process.
• SDLC is a structure followed by a development team within the software
organization.
• A Life Cycle Model defines phases , milestone, deliverables and evaluation
criteria for software development process.
• Various SDLC methodologies have been developed to guide the process
involved.

Classification: Restricted Page 29

 Software Development Life Cycle

Classification: Restricted Page 30

 Requirement Analysis
From deliverables such as Feasibility Report, Cost Benefit Analysis, Risk
Assessment, Business Use Cases, Vision Document the Requirement Analysis
phase is carried out which includes :
Elicitation,
Validation,
Specification and
Verification
Deliverables of
Requirement
Analysis Phase:
• Functional
Specification
Document
• Software
Specification
Document
Classification: Restricted Page 31
 Role of BA in Requirement Analysis
• Requirements Gathering - Workshop Facilitation, Interviews, Observation,
Research.

• Requirements Documentation - Business Requirements document,

Requirements Traceability document, Functional & Non Functional
Requirements documents.

• This is where the BA will also use their modeling skills to document business
requirements.

• Requirements Validation & Prioritization activities.

• Stakeholder Engagement.

Classification: Restricted Page 32

 Design Phase
In this phase the detailed functional requirements created will be
transformed into complex detailed system design including screen layouts,
business rules, process diagrams and other documents.

Deliverables of Design Phase:

• Design Document
• Technical Design Specification

Classification: Restricted Page 33

 Role of BA in Design Phase
• Review the solution documents.
• Work closely with solution designer and architects to ensure requirements
are clear.
• Keep the stakeholder engaged to reassure them their requirements are
implemented as specified in the business requirement artifacts. In some
projects, such as Agile projects, this part of the iteration will have close
involvement of stakeholders right through the SDLC.
• Manage the changes to requirements both from the business and from your
solution designer’s point of view through a change control process. It is a
great time to actively start using the Requirements Traceability Matrix.

Classification: Restricted Page 34

 Development Phase
In this phase the Developers convert a complete design into an information
system.

Reproducible code.

Classification: Restricted Page 35

 Role of BA in Development Phase
• The Business Analyst’s role is lighter during this phase. In small teams it can
happen that the BA is asked to clarify requirements or in Agile projects the
BA will be asked to review prototypes.

Classification: Restricted Page 36

 Testing Phase
Demonstrates that the developed system confirm to requirements as
specified in the Functional Specification Document. Conducted by QA team
and BA support, if needed.

Deliverables of Testing Phase:

• Test Plan
• Test Strategy
• Test Scripts
• Test Cases

Classification: Restricted Page 37

 Role of BA in Testing Phase
• During the testing phase the Business Analyst can assist with reviewing test
scripts to ensure all functional requirements are being tested.
• A business analyst will also get involved with defect prioritization in some
projects.

Classification: Restricted Page 38

 Release and Maintenance
• Includes the preparation of the system into a production environment and
resolution of problems identified in the test phases and ready to be
released at client site.
• Training manuals.
• Maintenance includes post implementation problems and add on request
by the client.
Deliverables :
• The Software Application.
• Test Case and Reports.

Classification: Restricted Page 39

 Current Trends in Business Analysis
• Don’t expect to get all the requirements upfront.
• Focus more on Business Analysis
• Focus on adding the business value
• Adoption of professional BA approach
• More communication
• Building better business cases
• Its always plus to be bit technical

Classification: Restricted Page 40

 Thank you!

Classification: Restricted Page 41