Business Analysis

(1)

Business Analysis

Inggang Perwangsa Nuralam, SE., MBA.

(2)

Part 1 As a Problem Solver

Hal ini berarti bahwa analisis bisnis merupakan sebuah upaya peamecahan masalah dan menambah nilai

organisasi.

Dengan Cara Apa?

Menyediakan Perencanaan, Peta (Road Map), Langkah-langkah, Metode Pengerjaan, dan Jalan Keluar Terbaik.

(3)

“Semua berawal dari Information Teknologi (IT)”

Paul, Debra (2010)

THE ORIGINS OF BUSINESS ANALYSIS

• Business Operations

• Management Decision - making

Development of new services and products

(4)

THE DEVELOPMENT OF BUSINESS ANALYSIS

Outsourced their IT services and functions

Competitive

advantage of using IT Successful business

change The importance of the

business analyst

The use of consultants

(5)

let’s discuss about “business”

as part of business analysis

(6)

Business operates

under various

Environment Constraints

(7)

Your Business Here

(8)

These Environment

Constraints acts as drivers

for Business Change

(9)

(10)

Business Analysis is now the

enabler for identifying “what” is

required to be done to achieve the

desired Change or Goal .

(11)

Business Analysis

Works with Teams to determine

“ How ” - The Solution

Domain Analysis Business

Analysis Identify the “ What ” -

Problem Domain

Analysis

(12)

Business

Change Cycle

(13)

In the beggining….

Projects were like a

battlefield…..

(14)

A lot of work was being done…..

But it was not

always productive

(15)

later on…..

Organization invested in

Project Management Practice

typical project lifecycle

Plan Build Test Implement

(16)

still unsuccesful result

it did not work

typical project lifecycle

(17)

• Only 16.2% of projects will be completed on time & on budget

• About 40-56%of project conflicts can be traced to requirement errors

• Finding and fixing requirement errors consumes 70-85% of project rework costs

• The average project exceeds its planned time schedule by 120%

• About 52.7%of projects will cost 189% of their original estimate

• About 30% of projects are cancelled before completion.

Why it doesn’t work?

(18)

…expends least effort on requirements analysis…

…which is where most errors originate…

…and whose errors cost most to fix!

Typical project…

(19)

That is why project is

doomed…

(20)

Now… The Picture is Complete

Plan Build

BusinessAnalysis

Project

Management

(21)

(22)

The Business Analyst in Context

(23)

The Definition of Business Analysis

IIBA* defines a Business Analysis:

The set of tasks & techniques used to:

1. Work as a liaison among stakeholders

2. To understand the structure, policies and operations of an organization

3. and to recommend solutions that enable the organization to achieve its goals.

adalah rangkaian tugas & teknik yang digunakan untuk: bekerja sebagai penghubung antara para pemangku kepentingan untuk memahami struktur, kebijakan dan operasi dari suatu organisasi dan merekomendasikan solusi agar suaut organisasi dapat mencapai tujuannya.

* Source: International Institute of Business Analysis (IIBA®)

(24)

Business Analysis new discipline that promises to offer great benefit to organisations by ensuring that business needs are aligned with implemented

business change solutions

.

Many of those solutions will involve new or enhanced information systems, but others may have a broader scope incorporating

changes to areas such as business processes and job roles.

Debra Paul, Donald Yeates and James Cadle , 2010

(25)

The Requirements

(26)

Requirement: IIBA’s Definition

A Requirement is defined to be:

1. A condition or capability needed by a stakeholder to solve a problem or achieve an objective;

2. A condition or capability that must be met or possessed by a system to satisfy a contract, standard, specification, or other formally imposed document.

3. A documented representation of a condition or capability as in (1) or (2).

Sebuah Kebutuhan didefinisikan sebagai:

Sebuah kondisi atau kemampuan yang dibutuhkan oleh pemangku kepentingan untuk memecahkan masalah atau mencapai tujuan; Sebuah kondisi atau kemampuan yang harus dipenuhi atau dimiliki oleh sistem untuk memenuhi kontrak, standar, spesifikasi, atau dokumen lainnya secara resmi dikenakan (sesuai yang berlaku);

Sebuah dokumen yang merepresentasikan dari sebuah kondisi atau kemampuan seperti pada (1) atau (2).

(27)

Business Analysis Practice

Business analysis is the practice of enabling change in an organizational context by defining needs and recommending

solutions that deliver value to stakeholders.

Analisis bisnis adalah praktek yang memungkinkan perubahan dalam konteks organisasi dengan mendefinisikan kebutuhan dan merekomendasikan solusi yang memberikan nilai bagi stakeholder.

(28)

(29)

THE SCOPE OF BUSINESS ANALYSIS WORK

“Different feedback from wide organisations have highlighted that business analysis job descriptions are unclear, a range of possibilities and do not always

describe their responsibilities accurately.”

One way in which we can consider the business analyst role is to examine the possible range of analysis activities.

(30)

POTENTIAL RANGE OF THE BUSINESS ANALYST ROLE

Strategic analysis and definition

Business analysis

IT systems analysis

Typically the work of senior management, often supported by strategy consultants

Analysing and specifying the IT system requirements in sufficient detail to provide a basis for the evaluation of software packages through data

modelling and process or function modelling

GAP

• Investigate a business system where improvements are required.

• Recommend actions that would overcome a problem or achieve business benefits.

• Focus specifically on enhancing or replacing an existing IT system in line with business requirements.

(31)

Taking a holistic approach

Organisation

Technology

People Process

(32)

The business analysis maturity model

(33)

The four views of a business system

(34)

(35)

principles for business analysis

1. Root causes, not symptoms: to distinguish between the symptoms of business problems and their root causes, and to investigate and address the root causes.

2. Business improvement, not IT change: to recognise that IT systems should enable business opportunity, to analyse opportunities for business improvement and to enable business agility.

3. Options, not solutions: to challenge predetermined solutions, and identify and evaluate options for meeting business needs.

4. Feasible, contributing requirements, not all requests: to be aware of financial and timescale

constraints, to identify requirements that are not feasible and do not contribute to business objectives, and to evaluate stated requirements against business needs and constraints.

5. The entire business change lifecycle, not just requirements definition: to analyse business situations and support the effective development, testing, deployment and post- implementation review of solutions.

6. Negotiation, not avoidance: to recognise conflicting stakeholder views and requirements, and negotiate conflicts between stakeholders.

7. Business agility, not business perfection: to enable organisations to be responsive to external pressures and to recognise the importance of timely, relevant solutions.

(36)

The business analysis maturity model

(37)

The capability maturity model integration