Business Analysis Training - Introdcution

info@myprojectanalysis.com | Ph: 732-707-1182 | www.myprojectanalysis.com
www.MyProjectAnalysis.com
Business Analyst Training Online
Mobile: 732.707.1182
Email: info@myprojectanalysis.com
1

Refreshment…
 What is a Project?
 How does project get started?
 What is the source of the project?
 Who are the Key players?
 Who are the stakeholders?
 Who are the SMEs?
2

Introduction to Business Analysis
 Introduction to Business Analysis
 How do you define Requirement?
 What is Elicitation?
 How Business Analysis is distinct from…
 Roles and Responsibilities
 Need for a Business Analyst
 Importance of a BA in the Project Team
 Skills Required
3

Business Analysis & Set of tasks:
Primary task: To Identify business needs
What are business needs?
• Identifying the business goals
• Understanding the business goals
• Identifying the business problems
• Determine solutions to business problems.
How do you categorize them?
• Business Analyst – Identifying & Understanding the goals or problem (What info)
• Systems Analyst – Solving the Problem (How info - Determine solutions)
• Business Systems Analyst - ??????
4

Responsibilities for Business Analysts on software
projects
 Extract: A BA determines the Requirements by extracting them from business
(and government) policies and, when possible, the current or future end users.
 Anticipate: A BA casts a vision to the Product Owner so she can anticipate
Requirements that are not yet needed or have not yet been considered (like
security).
 Constrain: A BA constrains the user’s whims – functions geared to trends,
individuals, or outdated processes – and focuses users on the core business
needs.
 Organize: A BA organizes disparate requirements into correlated categories for
to manage and communicate Requirements with technical, left-brained
resources.
5

Responsibilities for Business Analysts on software
projects
 Translate: A BA translates business Requirements into technical Requirements
(not solutions); abstracting business complexity away from technical resources.
 Safeguard: A BA safeguards the needs of business and system users in the
development process by verifying functionality, accuracy, and completeness.
 Simplify: A BA advocates simplicity all the time – especially in implementation,
making the system useful but continually focusing on day-to-day ease of use.
 Verify: A BA knows the use cases best. They advocate the users, verify the
system against Requirements, and must reject implementations that don’t hit
the target.
6

Business Analysis & Set of tasks: (Cont.)
If you put all together – Business Analyst works as a liaison
among stakeholders
• Will help to improve organizational change.
• Will collect data for business decision making
• Will identify strengths and weaknesses in the business
In other words: A Business Analyst works as a liaison among
stakeholders or SMEs in order to elicitate (collect), analyze,
communicate, and validate the requirements for changes to
business processes, policies, and information systems.
7

Key players for the project
 Project Owner / Sponsor
 Project manager
 Architects
 Stakeholders
 SMEs
 Developers
 Testing
 Configuration/Release Managers
 & Of course Business Analyst should manage and ensure project
moves on with no issues
8

Ok, How do you define Requirement?
 A condition or capability/feature needed by stakeholder or
 To solve a problem or
 To achieve an objective or
 To satisfy a contract
 Ex: Sample requirements for ATM machine.
 Capability- As customer, user should have a capability to
withdraw, Transfer or Deposit the funds
 Satisfy a contract– As a customer, user should not able to
withdraw the funds more than $800.00
 Ensure requirements are complete, clear, correct and consistent.
9

What is Elicitation?
 Elicitation – is a technique of collecting intelligence
information from people based on the project.
 Requirements elicitation is the practice of collecting the
requirements from users, customers and other stakeholders
using any of these techniques
 Interviews, Meetings, Observations, prototyping.
10

How Business analysis is distinct from
• Financial analysis,
• Project management,
• Data Analyst
• System Analyst
• Quality assurance,
• Training and
• Documentation development.
 However, depending on an organization, an individual Business Analyst
may perform some or all of these related functions.
11

Primary Responsibilities
 Elicitation – Discovering the underlying business need to be addressed
and information related to the product and project requirements, often
through conversations with stakeholders.
 Analyzing Requirements – Organizing, specifying and modeling the
requirements to ensure they are complete and unambiguous.
 Specifying Requirements – Documenting the requirements in a format
that can be shared with stakeholders.
 Validating and Verifying Requirements – Ensuring the requirements map
to the real business need, are approved by all relevant stakeholders, and
meet essential quality standards.
12

Need for a Business Analyst
 A business analyst works as a liaison among stakeholders and/or in
order to
 Elicitate, Analyze, Communicate & Validating requirements
 Documenting the requirements within the scope and eventually keeping
the project on track.
 In other words: BA understands business problems and opportunities
in the context of the requirements and recommends solutions that
enable the organization to achieve its goals.
13

Importance of a BA in the Project Team
 Acts as a bridge to convey requirements between the business customers and
the project-development team
 Should identify and document stakeholders with respect to the requirements
(who is important for what?)
 Required to ensure activities are completed in the most effective and efficient
manner possible.
It is likely that the Business Analyst may decide to communicate in different ways
using different methods to the different roles. i.e. formal presentations to the
Executive Sponsor and Project Manager while using emails and memos to the
project team members.
14

Skills required for BA
 Communication Skills
 Facilitator
 Listening Skills
 Minimal Technical Skills
 Analytical Skills
 Problem Solving Skills
 Managerial & Negotiation Skills
 In very common way BA should aim to change person's (or a team’s)
attitude or behavior towards requirements or project goal by using written
or spoken skills to convey information or reasoning's.
15

Principles to follow
1. Focus on the product
2. First define the problem and then the solution
3. Users do not have requirements
4. Focus on information not individuals
5. Separate Elicitation from Analysis
6. Improve the process first then add technology
7. Communicate cooperate, collaborate keep communications flowing in all directions
8. The business analyst owns solution requirement
9. Gain acceptance as well as approval
10. Make the Business communicate ready for the product
11. Measure twice, cut once.
16

BA Deliverables
 BRD – Business Requirement Document
 FRD – Functional Requirement Document
 TRD – Technical Requirement Document
 RTM – Requirement Traceability Matrix
 UML Diagrams, Workflows
 Prototypes
 Wire frames
 Test Plans
 Signoffs
17

Analysis & More…
 Enterprise Analysis
 Stakeholder Analysis
 Gap Analysis
 Impact Analysis
 Dependencies
18

Thank you!
19

Business Analysis Training - Introdcution

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Business Analysis Training - Introdcution

Similar to Business Analysis Training - Introdcution (20)

Recently uploaded

Recently uploaded (20)

Business Analysis Training - Introdcution