Business Analysis Approach

Project:
[Go to File | Properties and add the complete project name into the Subject area. Doing so will ensure you
only need to enter the project name in one spot and reference the Subject field however many times are
necessary. Perform an Edit | Select All, then F9 to update all Subject fields. Delete this when complete.]

Updated: 3/17/2011 10:42:00 AM

Author: [BA Resource Name]
BA APPROACH –

Approach
What will be covered in this plan are the responsibilities and work required for this project. The plan will
clearly depict what is expected for all Business Analysts and Rules Analyst resources as applicable.

Roles & Responsibilities

The roles fall into two categories, Business Analysis and Business Rules Analysis. Business Analysis
focuses on Business Requirements, User Requirements and Functional Requirements which are further
defined below with responsibilities. Business Rules Analysis focuses on the capture, model, craft and
authoring of Business Rules.
[Denote here if BA and BRA will be leveraged on your project, just the BRA, or just the BA, and then
delete this instruction.]
Business Requirements
These are the requirements that illustrate what the business problem is, what the business needs to
accomplish, and/or what are the business goals. The responsibilities include but are not limited to the
following:
• Leads the elicitation of business requirements with Business Representatives and Subject
Matter Experts
o Focusing on the why and what the business needs
o Measurable business benefits
• Collaborates with the business to prioritize business needs
• Documents clearly and consistently the business requirements statements in the project
charter
• Documents the High Level Process Model representing the business requirements in
Blueprint
• Ensures the business requirements truly meet the business needs as defined by the business
through collaboration and review sessions
• Collaborates with the PM to receive approval of the business requirements in the Project
Charter
• Receive approvals from Governance and Business Unit
User & Functional Requirements
These are comprised in a defined list of what the user needs to accomplish and how the user interacts
with the process. The responsibilities include but are not limited to the following:
• Creates business process models in Blueprint with user and functional requirements
including:
o Milestones, participants, decisions, inputs/outputs
• Documents User and Functional Requirements in Blueprint
o Receive approvals from Governance and Business Unit
• Leads High Level Design Discussion
• Leads playbacks in order to ensure that the evolving solution continues to meet the
requirements

PAGE 2
 BA APPROACH –

• Leads the development of user training materials and works with business to construct
appropriate curriculum
Rules Analysis
Rules analysis is comprised of the identification of decision points, terms and business rules. The
responsibilities include but are not limited to the following:
• Facilitate/lead rule harvesting sessions
• Documents new business terms in the concepts catalog (using RuleXpress)
• Drafts fact models using new concepts (using Visio)
• Identifies Decision Points in Process Models
• Captures Business Rules in Blueprint
[If a BRA will not be leveraged on your project then remove the Rules Analysis role definition and
responsibilities. Delete this instruction when complete.]

The table below represents the specific Business Analyst tasks assigned to this project and
corresponding deliverables as applicable. All BA tasks below will be performed by [BA Name(s)].
[If there are multiple BA’s assigned, then denote below who will be completing which deliverable if a
deliverable will not be a joint effort. Delete this instruction when complete.]

Tasks Deliverables Estimate Date

Hrs Complet
ed
Project meetings 1. None N/A

Review Existing 2. None N/A

Documentation

Create BA 3. BA Approach document

Approach*

Document Business 4. Project Charter – business requirements

Requirements* added

Elicit and Document 5. Process models for -

User and Functional
Requirements • [Process Name] As-Is
• [Process Name] To-Be

6. Requirements specification document

Peer Review of 7. Updated Requirements specification

Requirements document

Review Sessions 8. Sign-off on Requirements specification

Review and signoff 9. None N/A

on QC test cases

PAGE 3
 BA APPROACH –

Tasks Deliverables Estimate Date

Hrs Complet
ed
Answer / Support 10. None N/A
Questions on
Requirements

* These items have a checkpoint tied to them and may require a review with the BA Manager.

The table below represents the specific Business Rules Analyst tasks assigned to this project and
corresponding deliverables as applicable. All BRA tasks below will be performed by [BRA Name(s)].
[If a BRA will not be leveraged on your project then remove the Rules Analysis tasks table below. Delete
this instruction when complete.]

Tasks Deliverables Estimate Date

Hrs Complet
ed
Harvesting Session 1
Sessions
Session 2
Session 3

Capture Terms Decision point 1

and Rules
Decision point 2
Decision point 3

Fact Modeling

Review Decision point 1

Decision point 2
Decision point 3

Status
Meetings

PAGE 4