evolutionary development methodology

© Redwing Business Intelligence Ltd 2002 - 2015 Methodology

Evolutionary Development Methodology®

for Business Intelligence

Introduction

Slide 1

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

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

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®


1988 – Christmas in TorontoNational 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!


Principles of EDM®

• Evolutionary

• Incremental

• Collaborative

• Iterative

• Agile?


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


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


EDM® is end-to-end complete


Release Strategy

Release n Plan

Steering Group

Review,Assess,

Prioritise,Approve

Iterative Development

Release n

Assessment

Initiation(6 Steps)

Executive

Executive createsSteering Group

Is there a business case for a business intelligence programme?

If so, then create a Release Strategy and put the governance in place

Major Components

Reporting/KPI/

dashboarddevelopment

Project Management

Infrastructure Planning

Business Needsand

Analytic Themes

Project Planning

Governance

PrioritisationWorkshop

ReleaseStrategy

Planning theWorkstreams

Infrastructure Planning Fix the order

Release nBusiness

RequirementsDefinition

-what does the business need?

TechnicalAnalysis

Verify the data is available

Define/sketch/

prototype the business I͛view of the information

Define/sketch/


Validate that the proposed information will address the business need

Knowledge Transfer as required / agreed

Define/sketch/


Analysis/design/

buildDimensional model in SQL Server andAnalysis Services

Get a static copy of the necessary source data and build K͛scaffolding I͛to get it into

the data warehouse

Define/sketch/


Define/sketch/


Validate that the proposed information will address the business need

Define/sketch/


Analysis/design/

builddimensional model in SQL Server andAnalysis Services

Get a static copy of the necessary source data and build K͛scaffolding I͛to get it into

the data warehouse

Iterative development hand-in-hand with the business

Define/sketch/


Refinement of dimensional model

in the physical database and

K͛hypercube I͛data warehouse

Formal Extract, Transport, Transform, and Load process using Integration Services

Release nImplementation

-Quality

Assurance-

UserAcceptance

Testing

Infrastructure Build


Layered Architecture


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)

Technology (specific product layer)


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 Warehousedimensional 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

Organisation and Staffing


Architecture

Warehouse Development

User Liaison

Help Desk

Infrastructure Support

Reports Development

Acceptance Test

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

Discussion


Donna Kelly

[email protected]

0(781) 380-0181

www.redwing-bi.com

mailto:[email protected]

http://www.redwing-bi.com/

evolutionary development methodology

Data & Analytics