Enable Business
Intelligence Across the
Enterprise
William McKnight
McKnight Associates, Inc.
Agenda
1. The user perspective
2. Data stewardship
3. Program governance
4. User support
5. Public relations
6. Executive sponsorship
7. Workload balancing
The User Perspective
 Lack of familiarity
 Disbelief
 Lack of understanding
 Training, support and
workload issues
 Looking for the deeper
meaning
Activate the Users
 User Roles and Responsibilities:
•
•
Attending training before receiving an ID to BI
•
Providing feedback to the BI build team
Browsing the technical and business metadata
for information on data sourcing and data
definitions
Have a Data Stewardship Program
 “One” per major business subject area in BI
•
Or prospectively in the future in BI
 Business role
Data Steward Roles and Responsibilities
 Designing the transformation rules
 Contributing business metadata
 Understanding new usage needs
 Supporting the user community
 Data quality
Who determines the transformation rules that
determine the look of business intelligence data?
A. Business intelligence ETL
architect
B. Business intelligence data
modeler
C. Data stewards from the business
D. Data stewards from information
technology
E. Business SMEs
F. We don’t design and/or
transform our BI data
G. Combination of business and IT
0% 0% 0% 0% 0% 0% 0% 0%
H. Don’t know
A
B
C
D
E
F
G
H
BI Program Governance
 Interest in major additions of usage,
subject areas and data sources should be
brokered by this committee if any of:
•
Perceived ROI is used as a driver for company
efforts and therefore a forum is needed to
confirm and refine these estimates
•
•
Limited budget or people resources
Expansion of data and data uses may strain the
scalability of the environment
BI Program Governance Team
 Director, VP-level in data steward areas
•
Present and future data stewardship areas
 BI management team
All Users get Training Before Receiving
an ID
 Schedule it quarterly
 Taught ½ by IT, ½ by Business
Training Agenda
 IT led
•
•
•
•
•
•
Backgrounder – How we got here
Technology components overview
Generic tool training
Subject area orientation and data model
How to use the metadata
How to access IT support
Training Agenda
 Business/Data Steward led
•
•
How to USE the data for business gain
How to access business support
User Support Plan
 24 X 7 rotation: immediate response
•
•
•
ETL, DBA, system administration functions
Escalation plans for non-response
Key vendors: DBMS, ETL, Data Access
 Business hours on-call: data stewards
 Business hours clearing of intranet
queries
Have a BI Public Relations Program
 Branding name
 Culture understands BI is center for
corporate data
 Common elevator knowledge intra-and
inter-team and users
 Subject-area orientation
 Common file server and intranet
Public Relations
 User e-mail/voicemail lists
•
•
Outage notifications
Planned and actual enhancements
 Improve the capture and clearing of BI
requirements
 Intranet page
•
•
Data model
Q&A forums
Executive Sponsorship and High Visibility
 BI must have visible support at C-Level
 Business role
•
EVP – marketing, finance, sales, product
management
 Strive for recognized BI contribution to
company’s most egregious challenges
Executive Sponsorship Roles and Duties
 Knowledge of BI systems
 Leadership in corporate governance
 Knowledge of shop BI environment
 Keeping BI out of internal cross-fire
Three Types of Work Orders
 Major enhancements
•
Comes under project procedures
 Minor enhancements
•
Comes under customer service request
procedures
 Errors and “How to”
•
Comes under service-level agreement
procedures
Allocate some measure of each iteration to minor enhancements (“Stack”)
Errors, Major and Minor
Enhancements
Minor Enhancements
Users
Errors and
“How to”
SLAs Needed
BI Dev Team
Help Desk?
Errors
System Admin
Major Enhancements
BI Advisory
Business Intelligence Iteration Plan
March
2004
June
2004
September
2004
December
2004
Phase 6
Phase 7
Planning
for Phase
7
Phase 8
Planning
for Phase
8
Project Procedures – Timelines
N-3x
days
N-2x
days
N-2x
days
DETAILED
REQUIREMENTS
PRIORITIZE
SCOPE
REQUIREMENTS
IDENTIFY
POTENTIALS
N-7
days
N-0
days
BEGIN
ITERATION
N-4x
days
SIGN OFF
N-4x
days
This completes the PLANNING Phase of a Project
Business Intelligence Process Model
Readiness
Assessment
Logical
Modeling
Physical
Design
Team Roles
Assignment
Technical
Architecture
ETL Build
and Test
Prioritization
Analysis
Application
Design
End-user
Access Layer
Build
Source
System
Analysis
Source to
Target Maps
Testing and
Quality
Assurance
Requirements
Definition
Build Plan
User
Acceptance
Planning
Architecture
Implementation
Enabling Business
Intelligence Across the
Enterprise
William McKnight
McKnight Associates, Inc.
www.mcknight-associates.com
(214) 514-1444