Bite sized training sessions fundamentals of business analysis
Download
1 / 21

Bite sized training sessions: Fundamentals of Business Analysis - PowerPoint PPT Presentation


  • 156 Views
  • Uploaded on

Bite sized training sessions: Fundamentals of Business Analysis. Objectives. Analyse the reasons why the fundamental components of all Business Analysis tools and methods must be the same Examine fundamental components of Business Analysis.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Bite sized training sessions: Fundamentals of Business Analysis' - cachez


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Bite sized training sessions fundamentals of business analysis l.jpg
Bite sized training sessions:Fundamentals of Business Analysis


Objectives l.jpg
Objectives

Analyse the reasons why the fundamental components of all Business Analysis tools and methods must be the same

Examine fundamental components of Business Analysis


Slide3 l.jpg

Setting the scene: scope of the Business Analyst role

…involving up to 10 groups of people…

Owners

defines measures of success and $targets

…Business Analysts confirm & document

$Money!

Strategists

determine the strategy to hit the targets

…Business Analysts help do market research, create strategy, challenge & document

Sponsors

establish a Programme that delivers the strategy

…Business Analysts document Programme TOR and help build the Business Case

Programme Managers

Institute Projects that implement the programme

…Business Analysts document the Project TOR

Project Stakeholders

…Business Analysts specifyrequirements for Projects (in the Business Model)

Design Analysts

designsolution that satisfies the requirements

…Business Analysts write functional specifications, protect requirements & document compromises

Solution Builders

buildsolution

…Business Analysts protect requirements & document compromises

Solution Builders &Business

testsolution

…Business Analysts ensure tested against requirements

  • Project managers

  • Implementsolution

  • …Business Analysts help with

  • Process and data migration

  • Cutover planning

  • Rollout

  • Users

  • Acceptsolution

  • …Business Analysts help with

  • $MEASURING $BENEFITS $REALISATION

POST-IMPLEMENTATION

Business Analysts feed back to the Owner how well their measure of success has been achieved

There is a chain of reasoning that leads from the statement of a problem to the implementation of solutions…


Chain of reasoning l.jpg
Chain Of Reasoning:

Change Requirements must be assumed to be wrong until they are provedto be right

Stakeholders


Scope of analysis of change requirements l.jpg
Scope of analysis of change requirements

Change requirements can be for (amongst others)

Processes

Organisation units

Locations

Channel

Data

Applications

Technologies

Non-functionals

…oh – and the valid intersections!!!


Change requirements scope example l.jpg
Change Requirements Scope - Example

  • We need to change how we take orders (process)…

  • …by the tele-orders team (organisation unit)…

  • …at our Leeds contact centre (location)…

  • …by phone or email (channel)

  • …to capture alternate delivery addresses (data)…

  • …on the Chordiant system (application)…

  • …running on the intranet (technology)…

  • …and make it available 24/7/365 (non-functional).



All the links in the chain of reasoning l.jpg
All the Links in the Chain Of Reasoning

Description

Driver

The problems / opportunities that the business face

Addressed as

measured by

The measures and targets that will enable us to declare the change project has been successful

Project

Objective

Delivered by

Definitions of what changes are required that will affect the measures of success (objectives) sufficiently for the project to be declared successful

Change

Requirement

Enforces

What rules must be implemented by the changes specified in the requirements

Business Rule


How to forge links in the chain of reasoning l.jpg
How to forge links in the Chain Of Reasoning

Business…

Functional…

Non-functional…

…high level

…mid level

Process model

Process specification

Non-functional specifications

Data model

Attribute specification

…low level

Analysis products

Driver

Problem / opportunity analysis

Addressed as

measured by

Specific – there is a precise definition of the objective

Measurable – there are units that the objective will be measured in

Achievable – the measures can be achieved ‘in the real world’

Relevant –this project will actually affect this objective

To-die-for – the project has failed if it does not achieve the objective

Project

Objective

SMART objectives

Delivered by

Change

Requirement

Enforces

Business Rule


All methods and all approaches have to cover all links in the chain of reasoning l.jpg
All methods and all approaches HAVE to cover all links in the Chain Of Reasoning

AKA…

Problems

Opportunities

Threats

Constraints

Agile “product backlog”

7 types of ISEB requirements

6 types if IIBA requirements

Driver

Addressed as

measured by

Vision

Benefit

Target

Agile “product backlog”

More process and data modelling

than you can shake a stick at

Project

Objective

Delivered by

Change

Requirement

Enforces

Business Rule


Example way of documenting l.jpg
EXAMPLE the Chain Of Reasoning way of documenting…

Driver

Problem / opportunity analysis


Slide12 l.jpg

EXAMPLE the Chain Of Reasoning way of documenting…

Driver

Problem / opportunity analysis

Addressed as

measured by

Project

Objective

SMART objectives


Slide13 l.jpg

Business… the Chain Of Reasoning

Functional…

Non-functional…

…high level

…mid level

EXAMPLE way of documenting…

Driver

Problem / opportunity analysis

Addressed as

measured by

Project

Objective

SMART objectives

Delivered by

Change

Requirement


Slide14 l.jpg

Business… the Chain Of Reasoning

Functional…

Non-functional…

…high level

…mid level

Process model

Process specification

Non-functional specifications

Data model

Attribute specification

…low level

EXAMPLE way of documenting…

Driver

Problem / opportunity analysis

Addressed as

measured by

Project

Objective

SMART objectives

Delivered by

Change

Requirement

Enforces

Business Rule


Slide15 l.jpg

  • A BA can request one of 4 types of support: the Chain Of Reasoning

  • Phone or email based query about a specific point

  • Informal review of a project deliverable

  • Formal review of full set of project deliverables

  • Facilitated workshop of how to apply analysis to a specific project

  • 1. In the case of phone or email query about a specific point

  • the BA poses the question and the training provider will provide guidance for how the technicalities of Business Analysis apply to the problem

  • Informal reviews of project deliverables will be done by email and will only discuss the technicalities of Business Analysis in relation to the document

  • Formal reviews will involve the BA sending the full set of Analysis deliverables to the training provider who will critique them from a technical perspective and then deliver the feedback in a one-to-one structured feedback session on the client site

  • Facilitated workshops will be initiated by the BA - the training provider will supply workshop agenda and prerequisites which the BA will use to organise the workshop. The training provider will then facilitate the workshop for the project.

Process execution rules

  • Who is interacts with process

  • Where they are

  • Availability of process

  • Volumetrics

  • Performance of process

  • Security & Authorisation levels

Non-functional Rules

EXAMPLE PROCESS RULES

Time to start

Training course

BA requests

support

Provide

BA support

Conduct

Training

Analysis Phase

Of Project

concludes

Monitor

Analysis

quality

Process dependency rules


Slide16 l.jpg

Non-Functional Rules the Chain Of Reasoning

Data content rules

  • Who is allowed access to the data?

  • How long must this data be kept?

  • How many instances of it must be supported?

  • Course.Start Date

  • Definition: the date/time the course is scheduled to start

  • Data type: Numeric

  • Size: 12

  • Domain: Datetime

  • Data rules:

  • Format is DD/MM/YYYY HH:MM

  • When created must be in the future

  • Cannot be a Saturday or Sunday or Bank Holiday

  • Attributes

  • Name

  • Start Date

  • Course duration

  • Attributes

  • Name

  • Contact details

  • Attributes

  • Name

  • Description

  • Attributes

  • Name

  • Content

  • Review feedback

EXAMPLE DATA RULES

Course

Attends

Delegate

Support Type

receives

Supplies

Data relationship rules

Analysis

Deliverable


Conclusions l.jpg
Conclusions the Chain Of Reasoning

  • There is a chain of reasoning that leads from the statement of a problem to implemented solutions

  • It doesn’t matter how you get from problem to solution – what method or approach – but you will HAVE to…

  • Define the problem being fixed (drivers)

  • Define how you will know they have been fixed (objectives)

  • Define what has to change to achieve objectives (high level requirements)

  • Define how big the changes have to be to achieve objectives (scope)

  • Define what process changes are required (process requirements)

  • Define what data changes are required (data requirements)


Ba q a i tor l.jpg
BA Q&A (I) - TOR the Chain Of Reasoning



Questions l.jpg
Questions? the Chain Of Reasoning