foolproof business intelligence

Fool Proof BI Delivery

Ross [email protected]

How Will We Build It?

How Will You Run It?

DELIVERY

• Requirements Definition• Planning & Design• Technology & Delivery• Build and Test• Ownership Handover

• Governance• Security• Management• Quality• Training

What Can We Give You?

What Do You Want?

DISCOVERY

• Background Knowledge• Competitor Solutions• Known Requirements• Vendor Solutions• Educational Workshops

• Strategic Vision• Corporate Plans• Systems Investigation• Data Analysis• Business Workshops





What Do You Want?

DISCOVERY DELIVERY






Management

Consultant

ProjectManager

BackgroundKnowledge

CompetitorSolutions

Known Requirements

VendorSolutions

Strategic Vision

CorporatePlans

SystemsInvestigation

DataAnalysis

What Do You Want?

What Can You Give Us?

EducationalWorkshops

BusinessWorkshops


What Do You Want?

History, Skills & Experience Audit1. List of all previous BI projects with sponsors, champions, implementers, supporters, success/fail details, technologies.

2. List of all employees with qualifications, experience, skills or interests applicable to BI.

3. Merged table of technologies and vendors ranked by skill competency and cultural acceptance.

Rational:a. To avoid cultural or technical push or pull

to certain products or technologies.b. To provide the basis of a BI teamc. To identify potential blockers and

champions.



DISCOVERY

Area Enterprise Department Individual

Business Analysis ITC 4

DBA ITCSales

21

Excel AccountsMarketing

Cognos 3

Hyperion

Oracle Current main databasetool

ITC 6

Business Objects 2002-2007Tool of Choice

TM1

Teradata

Datastage ITC 1

SQL Server ITC 1


What Do You Want?

Market Research1. Information oobtained from vendors, the internet, business publications, former employees or just by calling the competitors and asking them!

2. Table of business areas with the most popular technologies and vendors.

Rational:a. Implementation and on going support

and management will be easier if peers use the same technology.

b. Staff who move from peer to peer will be familiar with the technology.

c. Avoidance of risk in implementation (its been done before).

d. Reduction of cultural “pushback” if the same technology is in use elsewhere.



DISCOVERY

Area Competitor 1 Competitor 2 Competitor 3l

Sales Analyse Excel based Unknown Cognos

HR Reporting Peoplesoft Module Excel Cognos

Production Oracle DatabaseHyperion

Oracle Database Oracle Database

Finance Cognos Oracle Finance Business Objects

Obtained from vendors, the internet, business publications, former employees, or just by calling the competitor and asking them!


What Do You Want?

DISCOVERY Project Scope and Requirements1. Review and discussion with sponsors and stakeholders (official and unofficial) of the project scope and requirements brief.

Rational:a. Many clients fail to fully articulate their

real requirements, and require assistance with scope and requirements facilitation.

b. The Sponsor frequently has no real knowledge of what the stakeholders really want.

c. Avoidance of misunderstanding and dispute later in the project.



What Do You Want?

Market Research1. Investigation into vendors and suppliers

to rank on the basis of history, future, problems, support etc.

2. Reference site visits.3. Review of respected rankings and

reviews, e.g. Gartner.4. Review of vendor capabilities in the

subject area

Rational:a. Buying into a BI technology is a long term

costly investment. The vendors and the products have to be “future proof” (no takeovers or bankruptcy), the vendors has to be investing in the future of the technology and the product must be free of problems.



DISCOVERY

What Do You Want?

Enthusiasm and Ideas1. Workshops covering history of BI, What it can do, Some examples of Dashboards, Reports, Predictive Analytics, with handoutsAnd whitepapers.

2. Follow up interviews to discuss and capture opportunities and potential ideas.

Rational:a. Enthusiasm and “buy in” are essential to

the success of a BI project. Staff need to feel part of the project, and will have good ideas for the best benefit that can be derived from BI.

b. Irrespective of the Project Scope or Requirements Definition, the workshops and interviews will bring out the real need for BI.


DISCOVERY


Strategic Vision Mapping1. A mapping table linking the Corporate Strategic Vision to the Business implementation of that Vision, and mapping it to the BI Enablement of that implementation.

Rational:a. Business Intelligence should be seen as an

enabler of the Corporate Vision.b. Vision Mapping provides guidance and

direction and prioritises effort.

What Can We Give You?• Strategic Vision• Corporate Plans• Systems Investigation• Data Analysis• Business Workshops


DISCOVERY

1. Xxxxxxxxx2. Xxxxxxxxx3. Xxxxxxxxxx4. Xxxxxxxxxx5. Xxxxxxxxxx6. Xxxxxxxxxx7. xxxxxxxxxx


STRATEGIC VISION

BUSINESSIMPLEMENTATION

BIENABLEMENT


1. Increased customer retention

1. 12% reduction in customer churn within 5 years.

Note – If the Business implementation of the Strategic vision does not exist – you will have to do it as part of the project


Strategic Planning

KPI's and Performance Management

P&L and Balance Sheet Analysis Reports

Balanced Scorecard

Financial and Management Reporting

Budgeting and Planning

Debtor Management & Planning

Cash Flow Forecasting

Assets & Asset Maintenance

Operational Analysis

Product Costing

Scenario Planning and Risk Analysis

Tax Planning and Analysis

Customer Gains & Losses

Compliance Reporting

Capacity Planning

Inventory Planning and Management

Headcount Analysis & Planning

Operational Cost Analysis

Asset & Depreciation Analysis

Activity Based Costing and Cost Models

Property Management

OH&S Incident Analysis and Costing

Team & Individual Performance Management

Project Analysis and Planning

Sales Analysis Feasibility Studies

Utilities Capacity Utilisation and Planning

Corporate roadmap1. A roadmap showing all major potential influences on the BI project, including planned system and organisational changes, and market and product changes..

Rational:a. Avoidance of risk of major changes

affecting decisions or delivery of the BI project.

b. Avoidance of potential competitor solutions or technologies arising during the project.



DISCOVERY

System and Organisational changes:

Market and Product changes:

2012

2013

2014

2015

New GL System Mainframe closeOffice 2010 New DW

Singapore OfficeProduct Release Plant Closures

CRM Change

EC2 Released to Market


Systems Mapping1. A mapping table covering all data generated by the corporate systems, including content, owner, and management team.

Rational:a. A systems mapping table will identify

duplicate sources of data, data dependency trails, owners etc.

b. The map is created from analysis of existing plans and documents, but with confirmation via research and investigation. Nothing should be assumed until it has been proved.



DISCOVERY

System A System B System C

Customer details QLD, NSW only All pre 2004 2011 only

Sales Records All (aggregated only) VIC pre 2004 Granular 2011

Production Details QLD, NSW only VIC only 2011 only

Date Created 2004 2000 2010

Owner/Custodian J Doe Smart Pty Ltd Finance


Data ReportA detailed data report covering:What: What data is available, what format, what content?When: Refresh times, dates, reloads, re-users?Quality: Error percentages, blank fields, exception reports?Validity: is the data valid for the intended purpose?Owner: Who claims ownership?Manager: Who manages the data on behalf of the owner?Access: How is access to the data achieved?Confidentiality: How confidential is the data?Security: What security classifications and procedures are in place?Structure: What structure or format is the data in?


DISCOVERY


Business Glossary1. A universally agreed and documented series of business definitions and measures and metrics obtained via focussed workshops.

Rational:a. No BI system can be implemented until all

business users achieve commonality in terms, measures and metrics. The easiest way of achieving this is via focused workshops.



DISCOVERY

Measure Defined Metrics

Customer A customer is any individual or group of individuals who enters into any form of communication with the enterprise with the intention of exchanging money for goods, services or advice.

Name, address, age, demographic group, sex, phone number.


Background Knowledge

Competitor Solutions

Known Requirements

Vendor Solutions

Educational Workshops

Strategic Vision

Corporate Plans

Systems Investigation

Data Analysis

Business Workshops

RequirementsDefinition


RequirementsDefinition

Planning&

Design

Technology& Delivery

MethodologyBuild &Test

Governance

Security

Management

Quality



OwnershipHandover

Training



DELIVERY



Requirements Contract1. An overlay of all of the work in the

Discovery phase, ranked and weighted to provide optimum value for money and cost effective business benefit, for the lowest risk of failure.

2. Agreed and signed off by all sponsors and stakeholders, as a contractual agreement.



DELIVERY


Roadmap and Design1. A high level roadmap for the delivery

of the project.2. Cost predictions and estimates.3. A set of conceptual and logical data

maps, selected data sources, report subject areas, mapping tables, high level designs.

4. Dummy dashboards, reports and interfaces.

5. Fallback and alternate strategy plans.



DELIVERY


Technology and Methodology 1. An evaluation of technologies, based

upon Phase 1 outcomes, pricing, suitability matrix and tender responses.

2. A purchasing cycle for any required technology.

3. A selected delivery methodology (Agile, waterfall etc.).

4. Infrastructure and Resource requirements requests.



DELIVERY


1. Resource management and control, including contractors, vendors and internal staff.

2. Risk management, including risk workshops, risk identification, risk treatment planning.

3. Status reports and milestone reporting, communication plans and stakeholder updates.

4. Scope and cost control.5. Task planning, tracking, work

allocation and performance monitoring.

6. Test plans and ongoing testing.

Delivery Management



DELIVERY


Handover1. User Acceptance testing2. User training3. Requirements tractability matrix

signoff.4. Pre production testing (stress, fail,

backup/restore etc.)5. Documentation of processes and

procedures.


How Will You Run It?• Governance• Security• Management• Quality• Training

DELIVERY

Governance1. Ownership, control and direction2. Future strategic direction3. Data stewardship4. Compliance management5. Security enforcement6. Management supervision7. Information value management8. Risk management9. Solution promotion and protection10. Information exploitation11. Corporate value for money.



DELIVERY

Security1. Physical security considerations.2. Server security considerations and

plans.3. Database security considerations and

plans.4. Application security considerations

and plans5. User security level matrix.6. New user approval process.7. On going security management

process8. Security testing and auditing plans.



DELIVERY

System Management1. Management responsibilities defined.2. Management team identified and

trained. 3. System SLAs and Data Interface

Contracts established. 4. Backup and DR plans in place5. Master Data Management

implementation6. Metadata management7. Reusable solution management8. Data model propagation and control



DELIVERY

Data Quality1. Data quality review processes2. Exception report action3. Data quality acceptability level

agreements4. Data quality audit processes5. Master Data Management



DELIVERY

Training1. User training and manuals2. Power user training and familiarisation3. Support staff training (IT dept. etc.)4. External course training (vendors)5. Helpdesk training6. Organise internal skills dissemination7. Contact list and “actions on”8. Upgrade and maintenance training.

Iterative Loop

TypicalBI

Applications



?Doesn’t take placeUsually guessworkOften rumourProject Manager makes it up.

Doesn’t take placeMade up as they go alongProject Manager ignores itClient thinks they can do it later.

What Usually Happens……




What Do You Want?

DISCOVERY DELIVERY





ProjectManager

Missing

Missing

Missing


The reason for the appalling success rate for BI projects….

There is more than just building it….

foolproof business intelligence

Technology

bi technology

fool proof bi deliveryross

history of bi

bi teamc

competitor solutions2

requirements vendor

future proof notakeovers

previous bi projects