Business Analysis Training

What is Business Analysis 

1. is the set of tasks and techniques used to work as a liaison among stakeholders, in order to undersand the structure, policies and operations of organization
2. recommend solutions that enable the organization to achieve its goals

Gather requirement and structure them in Structured report..
Set of task and technique used to work

Elicit requirement

Technique such as interview, focus, research,different ways to gather requirements 

Analysis and document requirement

Validate if requirement is within vision and scope of project.

We keep talking to business stock holders so they stick to project

Document and communicate requirement

Every body involved in requirement

Business stack holders

development team

Quality/testing team

UAT (user acceptance testers) or end user

AS IT BA, you will integrate different systems

BA role mostly comes in building phase..

Six sigma is a testing tool

Quality standard.. Really strong and rigid standards, or bench mark for quality.
Error rate for 6-sigma is 3.4 error per 1 million
Rigid rule
Companies with six-sigma required a strong structured knowledge

Business Analysis and Projects 

Project is a temporary endeavor undertaken to create a unique product, service or result

1. Initiation
2. Planning
3. Execution
4. Control 
5. Closure

Projects management perspective:
SDLC

1. Analysis *BA does it, gather, document
2. Design could mean flow chart, process , data modelling 
3. Development.,. coding, etc
4. Testing, QA team does (he does analyis what software need to do so making test cases)
5. Implementation 
6. Post implementation Support

Integrating the two prospectives: Typical Project Phases

Who starts projects

• It could be PM or Stack holder or anyone senior.Person will write a IT service request
• It has objective
• scope, and description

• and requirements

This requirement will be assigned to BA

Good organization will always have a formal structured approach
BA jobs have screen shots, so his job is easy..
It could be mini BRD or big brd.

Once BRD request is sent.. BRD will start analysis work, he is talking to people
You do analysis, screen shots, and thats become a Requirment Document

There is a one more piece.. validating and sign off. BA will distribute and approve the BRD

Project Manager is like a conductor for orcahster music,who is controlling the project.

1. BA is a leader or a chair person when comes to project
2. PM to see if BA BRD is done or not?
3. PM is not bothered if requirements are met or incomplete

Triple Constraints of Project Management

1. Cost 
2. Scope 
3. Time

In Real time.. planning committee  sit with business and plan, as how many projects, whats budget and how long this will take.

Based on time of project, Time, cost and Scope decided after we get project.


Business Analysis Accountability
Product scope: Features and functions that characterize a product , service or scope
Process Analysis : define the ASIS and TOBE states of the business

Project Manager
Project Scope Controlling, making service delivered

Product Scope Creep

1. There could be multiple things happening but scope is only defined to that specific BRD
2. Multiple teams can be writing BRD for same application
3. We are limited to our BRD
4. If we have 5 enhancements than we have to write 5 brd
5. If for existing project, you keep adding requirements, then you are expanding the scope
6. Scope creep can happen due to poor business analysis
7. or business owner is changing requirement now and then.

How to avoid scope creep

You can clearly specify management that these are out of scope and not documented initially

BA bringing 

1. Vision/Visibility via scope
2. Accountability
3. Tracebility

All documents must be signed off by project sponsor , so to ensure nothing changes in between.