Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Evolutionary Development Methodology

1,083 views

Published on

EDM is an agile, spiral methodology developed specifically for business intelligence. It is a complete end-to-end methodology including assessment, initiation, and delivery.

EDM incorporates a principles-based layered architecture, including business architecture, information systems architecture, and techology layers.

Published in: Data & Analytics
  • Be the first to comment

Evolutionary Development Methodology

  1. 1. © Redwing Business Intelligence Ltd 2002 - 2015 Methodology Evolutionary Development Methodology® for Business Intelligence Introduction Slide 1
  2. 2. What’s a Methodology? • Alistair Cockburn describes a methodology as: “everything you regularly do to get your software out. It includes who you hire, what you hire them for, how they work together, what they produce, and how they share. It is the combined job descriptions, procedures, and conventions of everyone on your team. It is the product of your particular ecosystem and is therefore a unique construction of your organization.” • Very differently, Redwing describes EDM® as: “this is how we do things around here, to deliver value to the business” © Redwing Business Intelligence Ltd 2002 - 2015 Methodology Slide 2
  3. 3. BI is not OLTP • Transaction Processing systems are typically marked by a large development, followed by implementation into production and a much smaller maintenance effort • Business Intelligence is utterly different: it is a never-ending story, with continuing evolution and no differentiation between development and maintenance • BI needs a radically different methodology © Redwing Business Intelligence Ltd 2002 - 2015 Methodology Slide 3
  4. 4. Methodology Roundup • Traditional Waterfall: the SDLC – Pride, Spectrum, SDM/70, PRINCE 2 • ‘The Agile Manifesto’ 2001 – Extreme Programming, Scrum • Spiral – Boehm, Du Pont, EDM® • The Release is the outer spiral of EDM® © Redwing Business Intelligence Ltd 2002 - 2015 Methodology Slide 4
  5. 5. 1988 – Christmas in Toronto National Congress Canadian Information Processing Society 'Twas the night before implementation and all through the house Not a program was working not even a browse. - - - And the user exclaimed with a snarl and a taunt, It's just what I asked for, but not what I want! © Redwing Business Intelligence Ltd 2002 - 2015 Methodology Slide 5
  6. 6. Principles of EDM® • Evolutionary • Incremental • Collaborative • Iterative • Agile? © Redwing Business Intelligence Ltd 2002 - 2015 Methodology Slide 6
  7. 7. Processes: the heart of the business • Business run on processes • Processes generate measureable data • Measuring that data means turning raw data into information • Good information is actionable information • Actionable information lets the business improve its processes © Redwing Business Intelligence Ltd 2002 - 2015 Methodology Slide 7
  8. 8. Releases: the heart of EDM® • The focus is delivering value to the business • Value is delivered in chunks • Chunks are prioritised by business value • Each chunk is called a Release • Typically, one Release corresponds to one business process • Knowing how we’re doing for the process, is the goal of delivering the Release © Redwing Business Intelligence Ltd 2002 - 2015 Methodology Slide 8
  9. 9. EDM® is end-to-end complete © Redwing Business Intelligence Ltd 2002 - 2015 Methodology Slide 9 Release Strategy Release n Plan Steering Group Review, Assess, Prioritise, Approve Iterative Development Release n Assessment Initiation (6 Steps) Executive Executive creates Steering Group Is there a business case for a business intelligence programme? If so, then create a Release Strategy and put the governance in place
  10. 10. Major Components Reporting/ KPI/ dashboard development Project Management Infrastructure Planning Business Needs and Analytic Themes Project Planning Governance Prioritisation Workshop Release Strategy Planning the Workstreams Infrastructure Planning Fix the order Release n Business Requirements Definition - what does thebusiness need? Technical Analysis Verify the data is available Define/ sketch/ prototype the business view of the information Define/ sketch/ prototype the business view of the information Validate that theproposed information willaddress thebusiness need Knowledge Transfer as required / agreed Define/ sketch/ prototype the business view of the information Analysis/ design/ build Dimensional model in SQLServer and Analysis Services Get a static copy of the necessary source data and build scaffolding to get it into the data warehouse Define/ sketch/ prototype the business view of the information Define/ sketch/ prototype the business view of the information Validate that theproposed information willaddress thebusiness need Define/ sketch/ prototype the business view of the information Analysis/ design/ build dimensional model in SQLServer and Analysis Services Get a static copy of the necessary source data and build scaffolding to get it into the data warehouse Iterative development hand-in-hand with the business Define/ sketch/ prototype the business view of the information Refinement of dimensional model in the physical database and hypercube data warehouse Formal Extract, Transport, Transform, and Load process using Integration Services Release n Implementation - Quality Assurance - User Acceptance Testing Infrastructure Build © Redwing Business Intelligence Ltd 2002 - 2015 Methodology Slide 10
  11. 11. Layered Architecture © Redwing Business Intelligence Ltd 2002 - 2015 Methodology Slide 11 Technology (Specific Product) Technology (Hardware, Networks, Infrastructure) Application (Systems, Components, Services) Data (Business Entities, Databases, Schemas) Information System (Data and Application) Business (Strategy, Priorities, Organisation)
  12. 12. Technology(specific product layer) © Redwing Business Intelligence Ltd 2002 - 2015 Methodology Slide 12 Extract, Transport, Transform, Load (ETTL) SQL Server Integration Services (SSIS) SQL Server Agent SQL Server Reporting Services (SSRS) Relational Database Relational Database & T-SQL Hypercube SQL Server Analysis Services (SSAS) Data Warehouse dimensional modelling physical build MDX KPIs Windows (e.g. authentication, Kerberos, Active Directory) SharePoint PerformancePoint Services for SharePoint Dashboard Designer PowerPivot Services for SharePoint SharePoint Designer Excel Services for SharePoint Total Solution Architecture (Business, System, Technical, and Product Architectures) Methodology and Governance Infrastructure Design and Build – SQL Server and SharePoint Install and Administer Programme Management PowerView for Cubes
  13. 13. Organisation and Staffing © Redwing Business Intelligence Ltd 2002 - 2015 Methodology Slide 13 Architecture Warehouse Development User Liaison Help Desk Infrastructure Support Reports Development Acceptance Test
  14. 14. Summary • EDM® is a methodology dedicated to BI • The principles of EDM® are – Evolution – Iteration – Collaboration – Incrementalism • EDM® delivers functionality in Releases • Why use EDM®? It works . . . a proven track record © Redwing Business Intelligence Ltd 2002 - 2015 Methodology Slide 14
  15. 15. Discussion © Redwing Business Intelligence Ltd 2002 - 2015 Methodology Slide 15 Donna Kelly donna@redwing-bi.com 0(781) 380-0181 www.redwing-bi.com

×