140 likes | 250 Views
Keeping your eye on the ROI!. Business Intelligence from an “ROI” perspective…. Agenda:. BI Projects: Traditional Projects How does that “Jibe” ? Another Approach Techniques Questions. BI Projects: The Promise. “C” Level Executives, Data Warehouses and Dashboards
E N D
Keeping your eyeon the ROI! Business Intelligence from an “ROI” perspective…
Agenda: • BI Projects: Traditional Projects • How does that “Jibe” ? • Another Approach • Techniques • Questions
BI Projects: The Promise • “C” Level Executives, Data Warehouses and Dashboards • Users will Surf and Drilling “Up, Down and all around…” • Data Warehouses will be “Active” • Data Warehouse projects will make you famous…
BI Projects: The Reality • “C” level executives may glance at a dashboard, but they don’t steer by it! • Decision makers don’t spend a lot of time surfing data, they call their “Go To” person and get the boiled down answer. • Data Warehouse projects are more likely to make you “Infamous”… • Creating yet another version of the truth • Threatening the existing providers of information • Unleash undeliverable user expectations
Traditional Projects • The traditional architecture • Source -> ETL -> ODS -> ETL -> DW • Then: DW -> ETL -> DM -> Tools, Portals… • Value Propositions • Visibility – The “Wind Tunnel” & smoke traces • Reporting and Analysis • Alerts and Triggers • Organic and Exogenous Information
How does that “jibe” with reality? • Expected versus Actual Use Cases • Analytical Users • Decision Makers • Time Horizons • Some facet on a time over time basis • Before, Now, Next • Multiple simultaneous perspectives • Business Transaction Lifecycle • Perspectives and Alternate Dimensions • Scenarios, Plans and Write-back
Emerging Approaches: • Operational BI • Low hanging Fruit • Number of Beneficiaries • EII versus ETL • Pulling “live” data versus compiling • Building a catalog of measures and metrics • Template Driven Presentation • Template Technologies: Simple and beyond • Benefits of Templates
What’s BI really all about? • “Actionable” Information • Data > Information > Knowledge > Understanding • What’s the difference between them? • Providing for Action • Right stuff in the right hands at the right time • Creating a “Destination for Action” • Get data • Draw attention or Alert • Provide for triggering action • Trigger the followup
What’s an ‘Agile” Approach? • User Stories versus Use Cases • Two heads are better than one • Test first: If you can’t explain how to test it then you don’t understand it well enough to build it! • Build just enough to get going and then evolve the functionality and platform • Don’t “Plan to throw one away anyway” – plan on continuous refactoring!
Techniques – Technology • Tools • EII • ETL • Temporary Data Structures • Materialized Views • Partitions and their uses • Template Driven Architecture • Source Acquisition • Presentation Configuration • BPM, Six-Sigma and Building Blocks
Techniques – Methodology • Every Team Member an Evangelist • The “Circle of Friends”: leveraging opinion leaders in the organization • The Importance of “Change Management” • Project Leadership • Short and Choppy Steps - Duration • Taking an Island “One” platoon at a time • Plan – but don’t take your plans too seriously
Methodology - continued • The many values of Pilots • Technology • Tools, Patches and Integration • Performance, dependencies • User Story Confirmation • Fingerspitzen-Gefeuler • How did Thomas Jefferson design the sidewalks at UVA? • Teamwork • Direct Team Interaction • Extended Team Interaction • A chance to find out what you don’t know you don’t know!
Review • ROI is: • We add to it by: • We can accomplish this through: • Which can be actioned in the BI project when we: • Questions?