Professional Documents
Culture Documents
Foolproof Business Intelligence
Foolproof Business Intelligence
Foolproof Business Intelligence
Competitor Solutions
Background Knowledge
Educational Workshops
Corporate Plans
Systems Investigation
Data Analysis
History, Skills & Experience Audit 1. 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 team c. To identify potential blockers and champions.
Cognos
Hyperion Oracle Business Objects TM1 Teradata Datastage SQL Server ITC ITC Current main database tool 2002-2007 Tool of Choice ITC
1 1
Market Research 1. 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.
Obtained from vendors, the internet, business publications, former employees, or just by calling the competitor and asking them!
Project Scope and Requirements 1. 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.
1.
2. 3. 4.
Market Research Investigation into vendors and suppliers to rank on the basis of history, future, problems, support etc. Reference site visits. Review of respected rankings and reviews, e.g. Gartner. 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.
Enthusiasm and Ideas 1. Workshops covering history of BI, What it can do, Some examples of Dashboards, Reports, Predictive Analytics, with handouts And 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.
Strategic Vision Mapping 1. 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.
1. 2. 3. 4. 5. 6. 7.
1. 2. 3. 4. 5. 6. 7.
1. 2. 3. 4. 5. 6. 7.
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
Product Costing
Operational Analysis
Capacity Planning
Balanced Scorecard
Compliance Reporting
Sales Analysis
Feasibility Studies
Property Management
Corporate roadmap 1. 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.
Office 2010
New DW
New GL System
CRM Change
Mainframe close
Product Release
Plant Closures
Singapore Office
2012
2014
2013
2015
Systems Mapping 1. 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.
System A Customer details Sales Records Production Details Date Created QLD, NSW only All (aggregated only) QLD, NSW only 2004
System B All pre 2004 VIC pre 2004 VIC only 2000
Owner/Custodian
J Doe
Finance
Data Report A detailed data report covering: What: What data is available, what format, what content? When: Refresh times, dates, reloads, reusers? 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?
Business Glossary 1. 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.
Measure Customer
Defined 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.
Requirements Definition
Requirements Definition
Ownership Handover
Security Management
Quality
Requirements Contract 1. 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.
1.
2. 3.
4. 5.
Roadmap and Design A high level roadmap for the delivery of the project. Cost predictions and estimates. A set of conceptual and logical data maps, selected data sources, report subject areas, mapping tables, high level designs. Dummy dashboards, reports and interfaces. Fallback and alternate strategy plans.
1.
2. 3. 4.
Technology and Methodology An evaluation of technologies, based upon Phase 1 outcomes, pricing, suitability matrix and tender responses. A purchasing cycle for any required technology. A selected delivery methodology (Agile, waterfall etc.). Infrastructure and Resource requirements requests.
1.
2.
3.
4. 5.
6.
Delivery Management Resource management and control, including contractors, vendors and internal staff. Risk management, including risk workshops, risk identification, risk treatment planning. Status reports and milestone reporting, communication plans and stakeholder updates. Scope and cost control. Task planning, tracking, work allocation and performance monitoring. Test plans and ongoing testing.
1. 2. 3.
4. 5.
Handover User Acceptance testing User training Requirements tractability matrix signoff. Pre production testing (stress, fail, backup/restore etc.) Documentation of processes and procedures.
Governance 1. Ownership, control and direction 2. Future strategic direction 3. Data stewardship 4. Compliance management 5. Security enforcement 6. Management supervision 7. Information value management 8. Risk management 9. Solution promotion and protection 10. Information exploitation 11. Corporate value for money.
DELIVERY
How Will You Run It?
Governance Security Management Quality Training
1. 2.
3. 4. 5. 6. 7.
8.
Security Physical security considerations. Server security considerations and plans. Database security considerations and plans. Application security considerations and plans User security level matrix. New user approval process. On going security management process Security testing and auditing plans.
DELIVERY
How Will You Run It?
Governance Security Management Quality Training
1. 2.
3. 4. 5. 6. 7. 8.
System Management Management responsibilities defined. Management team identified and trained. System SLAs and Data Interface Contracts established. Backup and DR plans in place Master Data Management implementation Metadata management Reusable solution management Data model propagation and control
DELIVERY
How Will You Run It?
Governance Security Management Quality Training
1. 2. 3.
4. 5.
Data Quality Data quality review processes Exception report action Data quality acceptability level agreements Data quality audit processes Master Data Management
DELIVERY
How Will You Run It?
Governance Security Management Quality Training
1. 2. 3. 4. 5. 6. 7. 8.
Training User training and manuals Power user training and familiarisation Support staff training (IT dept. etc.) External course training (vendors) Helpdesk training Organise internal skills dissemination Contact list and actions on Upgrade and maintenance training.
DELIVERY
How Will You Run It?
Governance Security Management Quality Training
Iterative Loop
Typical BI Applications
Doesnt take place Usually guesswork Often rumour Project Manager makes it up.
Doesnt take place Made up as they go along Project Manager ignores it Client thinks they can do it later.
Fool Proof BI Delivery The reason for the appalling success rate for BI projects. DISCOVERY What Do You Want?
Background Knowledge Competitor Solutions Known Requirements Vendor Solutions Educational Workshops