Agile BI With SQL Server 2012

Transcription

1 Agile BI With SQL Server 2012

2 Agenda About GNet Group Level set on components of a BI solution The Microwave Society Evolution & Change Approaches to BI Classic Agile Blend of both approaches Agility with Microsoft SQL Server 2012 PowerPivot Demo 2 Scenario s In Summary

3 About GNet Group Managed Gold Certified Partner focused on Empowering Data Driven Strategies Leading Provider of Microsoft BI and SharePoint Solutions Over 175 projects across multiple verticals SQL 2012 RDP Partner Leading Provider for SharePoint Development Finalist for Global Business Intelligence Partner of the Year 2011 HQ in Minneapolis, local office in Dallas, offshore development center in Pune, India

4 Level Set Food for Thought Components of a BI solution? 1. ETL (Extract, Transform, Cleanse, Load) 2. Data Warehouse (includes ODS, Staging, Dimensional Model) 3. Presentation (OLAP, Reports, Dashboards, etc.) Which of the above 3 can we get rid off and still deliver a long term & robust Ent. BI solution? None! Enterprise Data Integration & Architecture is key to a successful Enterprise BI Solution

5 The Microwave Society Pace of business and short attention span Exponential growth in data, sources and reporting needs Reduced cycle times and pressure to react faster Need to deliver on reporting needs today The next business question is already here! Can we deliver an Enterprise BI solution tomorrow? Next week? Next month?

6 BI Solutions Must and Will Evolve Changes in DW Transparency: Report what happened? (DW and Reports) Challenges 1. Ent Data Architecture 2. Time Improvements Measure change impact (Evolve DW, Dsh, Rpts) Processes & Data Discover & Question what s happening? (Dashboards and Ad-Hoc Analysis) Changes What should happen? (Goal and process) Understand Why? Cause & Effect? (root cause & predictive analytics)

7 Classic Approach to BI Ent Data Integration & Architecture X Time 80%-backend work takes too long May 12 November 12 Jun-12 Jul-12 Aug-12 Sep-12 Oct-12 Technical Architecture Design Technology & Infrastructure Install and Configuration Project Planning Business Requirements Definition Dimensional Modeling Physical Design ETL Design & Development Deployment BI Application Design BI Application Development 20%-touch & feel at project end Program / Project Management How often do requirements evolve during design/development? How often do requirements change and impact design/development? How often are the requirements and data in sync? How does the above impact design/development? How fast can we change a DW / ETL to align with changing requirements?

8 Agile Approach to BI X Ent. Data Integration & Architecture Time What about data integration, i.e. Ent Data Warehouse? One EDW vs. siloed data marts What about multiple perspectives of data (e.g. sales hierarchy, marketing hierarchy)? What about single source of truth? (e.g. Multiple Data marts sales, marketing) Can we rebuild / change data marts without impacting reports? How can we build a single, consistent enterprise data warehouse over time?

9 Blend the Two? 3. Project Planning 4. Business Questions and Requirements 9. Backlog For Each Roadmap Phase 5. Data Arch & Int 8. Feedback Data Warehouse build In parallel 7. Deploy Self Service 6. Prototype (BI App) Model Design Dev Ent Data Architecture Time: Early results. Buy time for Data Architecture End Goal is a comprehensive BI solution (ETL, EDW and Presentation) Agile BI Solutions in the interim while Data Architecture is built Ent. Data Architecture: ODS, EDW based on Exploration, Evaluation and Evolution. Accelerate robust EDW build based on solid requirements and feedback

10 How Does SQL 2012 Fit In? 3. Project Planning 4. Business Questions and Requirements 9. Backlog 1 st Iteration: PowerPivot For Each Roadmap Phase 2 nd Iteration: Team BI with SharePoint & PowerPivot or org BI - SSAS 5. Data Arch & Int Data Warehouse built in parallel Ent Data Architecture 8. Feedback 7. Deploy Self Service 6. Prototype (BI App) Model Design Dev Time: Early Results. Buy Time for Data Architecture Time : Agile, self service personal (PowerPivot) and/or team BI (PowerPivot for SharePoint) Promote PowerPivot to SSAS (Org BI) Some applications will remain in PowerPivot (Personal / Team)

11 Personal BI PowerPivot for Excel Team BI PowerPivot for SharePoint Organizational BI Analysis Services (OLAP) + SharePoint

12 New in SQL 2012 Analysis Services: BI Semantic Model One Model for All End User Experiences Client Tools Analytics, Reports, Scorecards, Dashboards, Custom Apps BI Semantic Model Personal BI PowerPivot for Excel Team BI PowerPivot for SharePoint Organizational BI Analysis Services Data Sources Databases, LOB Applications, Data Feeds, Spreadsheets, Text Files

13 PowerPivot Demo View our video: Create a PowerPivot BI Dashboard from Raw Data in Less Than 20 Minutes For a personal viewing of our demo, please contact AgileBI@gnetgroup.com.

14 Scenario 1: First DW (end goal is EDW) Personal BI Team BI Organizational BI Power Pivot for Excel XLS Power Pivot for SharePoint Promote to IT Managed Environment Process & Security PowerPivot Performan ce Point Excel and Excel Services SSRS BI Semantic Model ODS EDW Analysis Services CRM ERP POS Other SOURCE DBs CRM ERP POS Other Agility and long term data architecture!

15 Scenario 2: Additions to Existing DW Personal BI Team BI Organizational BI Power Pivot for Excel XLS Power Pivot for SharePoint Promote to IT Managed Environment Process & Security PowerPivot BI Semantic Model Performan ce Point Excel and Excel Services SSRS ODS EDW Analysis Services CRM ERP POS Other SOURCE DBs CRM ERP POS Other Agility and long term data architecture!

16 Evidence of the Blended Approach Pentair Technical Products Price Realization Project Polaris Industries Off-Road Vehicle Manufacturer Is Creating a Self-Serve BI System to Boost Product Quality Microsoft Case Study Manufacturer-Is-Creating-a-Self-Serve-BI-System-to-Boost-Product-Quality/

17 Benefits Blended approach addresses both Data Architecture and the Need for Speed Prototyping 1. Visualizing, touching, feeling the data facilitates discovery and exploration 2. Enables data profiling, validate requirements 3. Keeps customers engaged and involved in the process 4. Focus is on business discussion vs. technical specifications 5. Facilitates ownership and adoption Classic Approach based on feedback 1. Accelerates Data Architecture (EDW) build in parallel based on solid requirement 2. Perception of speed, they see activity, no big gaps in time, pressure relief valve 3. Removes the unknown which results in uncertainty and a sense of risk 4. Reduces cost of Data Architecture build Leadership can see the value in action

18 In Summary Need to blend Agile and Classic approach Why PowerPivot? Modeling and building the solution at the same time Can promote model/solution to enterprise class BI Solution This approach does not eliminate EDW- changes how we approach data architecture and time Biz/IT engagement- partnership is still key Roadmap and periodic (90 days) refactoring / re-prioritization Must Enable self-service to accelerate results and adoption Incorporate prototyping & deploy to production touch & feel ASAP! Gather feedback for long term data architecture Execute on it too! EDW is a must Technical architecture for SQL Server 2012 in-memory technologies Yes! Training and hands-on experience with 2012

19 Follow us! Blog: LinkedIn: Twitter: YouTube: Neelesh Raheja VP Consulting Services Greg Beaumont Solutions Architect Paul Doyle Solutions Architect