75
Helping Companies Learn From the Past, Manage the Present and Shape the Future July 11, 2013 www.senturus.com Agile BI Demystified Part of the BI Demystified Series

Agile BI Demystified - Senturus Business Analytics ... · • What is Agile & Why? • Why Agile BI ... Test Release Limited Stakeholder ... VALUE?! Model! Stakeholder! Input! Requirements!

Embed Size (px)

Citation preview

Helping Companies Learn From the Past, Manage the Present and Shape the Future

July 11, 2013 www.senturus.com

Agile BI Demystified

Part of the BI Demystified Series

How to ask questions via GoToWebinar!

Download a Copy of this Slide Deck "http://www.senturus.com/recorded-webinars.php"

Agenda

•   Introduction

•   What is Agile & Why?

•   Why Agile BI (vs. traditional approaches)?

•   Modelstorming

•   BEAM

•   More Resources & Next Steps

•   Q&A

Welcome and Introduction

John Peterson Co-founder and CEO

Senturus

Lawrence Corr Data Warehouse Designer, Educator

and Author of Agile Data Warehouse Design:

Collaborative Dimensional Modeling, from Whiteboard to Star

A Few of our 650+ Clients…

Critical Success Factors

•   Architectures & Data Transformation

•   BI Tools

•   Methodologies & Techniques

•   People & Processes

Parts of the BI Demystified Series

Critical Success Factors

•   Architectures & Data Transformation

•   BI Tools

•   Methodologies & Techniques

•   Dimensional Modeling & Data Warehouse Design

•   People & Processes

Parts of the BI Demystified Series

Agile? !

Why!

Why wait 18 months for the software you don’t want…!

— anon!

when you can have the software you don’t want in 28 days…!

— anon!

is Agile? !

What !

agile (adjective)!

able to move quickly and easily!

active; lively!

mentally quick or acute!

The Agile Manifesto !

•   We are uncovering better ways of developing software by doing it and helping others do it. "Through this work we have come to value:!

•   Individuals and interactions over processes and tools  !

•   Working software over comprehensive documentation !

•   Customer collaboration over contract negotiation  !

•   Responding to change over following a plan!

•   That is, while there is value in the items on the right, we value the items on the left more. !

1.   Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.!

2.   Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.!

3.   Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter time scale.!

4.   Business people and developers must work together daily throughout the project.!

5.   Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.!

6.   The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.!

7.   Working software is the primary measure of progress.!

8.   Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.!

9.   Continuous attention to technical excellence and good design enhances agility.!

10.   Simplicity – the art of maximizing the amount of work not done – is essential.!

11.   The best architectures, requirements, and designs emerge from self-organizing teams.!

12.   At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. !

12 Principles of Agile Software Development!

12 Principles of Agile Software Development!

1.   Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.!

2.  Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.!

3.  Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter time scale.!

4.   Business people and developers must work together daily throughout the project.!

5.   Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.!

6.   The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.!

7.  Working software is the primary measure of progress.!

8.   Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.!

9.   Continuous attention to technical excellence and good design enhances agility.!

10.  Simplicity – the art of maximizing the amount of work not done – is essential.!

11.   The best architectures, requirements, and designs emerge from self-organizing teams.!

12.   At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. !

Agile DW/BI? !

Why!

is Non-Agile DW/BI? !

What !

Traditional (waterfall) DW/BI Development!

Analysis

Design

Development

Test

Release

Limited Stakeholder interaction!

DATA!VALUE?!Data!

Model!

Stakeholder!Input!

ETL! BI!Requirements!

BDUF!Next Year!This Year!

Agile DW/BI Development!

Iteration n Iteration … Iteration 3 Iteration 1

VALUE! VALUE? VALUE VALUE! VALUE!

Iteration 2

Stakeholder interaction

Next Year This Year

Review Release

BI Prototyping ETL ?

Rev BI ETL ?

JEDUF

DATA

is in the box?!

What!

Entity Relationship Modeling – 3NF!

Dimensional Modeling – Star Schema!

Data !Driven!(Supply)!

Reporting!Driven!

(Demand)!Analysis!

De

sign!

Report-Driven Analysis!

Data" Modeler!

BI Stakeholders!

Business" Analyst!

BI Stakeholders!

BI Stakeholders!

Interview notes!

Report Specifications!

Requirement Document"

Data Models!

Database Schemas!

model collaboratively with Business people?!

Why !

Why Model with BI Stakeholders?!

•   Identify the significant business events worth measuring "Scope and Prioritisation "

•   Discover how business events are described "Dimensions"

•   Determine how they are measured"Measures, Hierarchies, Comparisons, KPIs"

•   Unearth budgets, forecasts, targets and other user-controlled data sources"Extra data, Common summarization levels: Physical Optimization "

•   Create business ownership and pride in the DW design!

Agile techniques could help?!

What !

! ! !Techniques and Terminology!

•   Scrum – Project Management!

•   ScrumMaster, Product Owner, Daily Scrum, Sprint, Product Backlog, Sprint Backlog, Burndown Chart"

•   Extreme Programming (XP) – Software Engineering!

•   User Stories, Daily Stand-Up, Iteration, On-Site Customer, Pair Programming, Test-Driven Development (TDD), Continuous Integration!

User Stories!

User Stories Usage Requirements!

Data Stories!

Data Stories Data Requirements!

kind of model can represent data stories?!

What !

CALENDAR

Date Key

Date Day Day in Week Day in Month Day in Qtr Day in Year Month Qtr Year Weekday Flag Holiday Flag

PRODUCT

Product Key

Product Code Product Description Product Type Brand Subcategory Category

PROMOTION

Promotion Key

Promotion Code Promotion Name Promotion Type Discount Type Ad Type

SALES FACT

Quantity Sold Revenue Cost Basket Count

Date Key Product Key Store Key Promotion Key

STORE

Store Key

Store Code Store Name URL Store Manager Region Country

What is a dimensional model, really?!

Verb!

Adverbs!

Noun! Noun!

Noun!Noun!

Adjectives!

Adjectives!Adjectives!

Adjectives!

can you model data with business people?!

How !

Data" Modeler!

Developers! BI Stakeholders!

Quick! Inclusive!

Interactive!Fun!

Modelstorming: Modeling + Brainstorming!

kind of model is fun for business folk?!

What !

CALENDAR

Date Key

Date Day Day in Week Day in Month Day in Qtr Day in Year Month Qtr Year Weekday Flag Holiday Flag

PRODUCT

Product Key

Product Code Product Description Product Type Brand Subcategory Category

PROMOTION

Promotion Key

Promotion Code Promotion Name Promotion Type Discount Type Ad Type

SALES FACT

Quantity Sold Revenue Cost Basket Count

Date Key Product Key Store Key Promotion Key

STORE

Store Key

Store Code Store Name URL Store Manager Region Country

NoSQL!

Not only "SQL!

NoERD!

Not only "Entity Relationship

Diagrams!

can help us?!

Who !

Ralph Kimball!

R. K.!

Rudyard Kipling!1865 – 1936!

I keep six honest serving-men "(They taught me all I knew);"Their names are What and Why and When "And How and Where and Who…!

— Rudyard Kipling"The Elephants Child!

6Ws!

Who !

What ! Why!

Where !

When !

How!Many!

How !5Ws!

7Ws!

How !

How

!W

hy!

How!Many!

Receipt !

Promotion!

Quantity!Revenue!

Cost!

BEAM Business Event Analysis & Modeling

Ho

w

Wh

y

How!Many

How Many!

does ?!When!

Who!

What!

Where!

Why!

How!

How Many!

Who! What!

Who does what?! (that we need to measure next)!

(Responsible) Subject Verb Object!

Customer buys product!

BEAM✲ Modeler! BI Stakeholders!

NoERD!

Model as a BEAM✲ Table – an Example Data Model!

buys!

CUSTOMER! PRODUCT!

[who]! [what]!

Details

Event Stories (4-6 rows)

Subject Column Name

Object Column Name

Verb

Column Type

Event Name (filled in later)

does a customer buy a product?!

When !

Example Stories!

does a customer buy a product from?!

Who !

Adding a Second Who Detail!

does a customer buy a product?!

Where !

How Many !

does a customer buy a product on... ?"

Why !

does a customer buy a product?"

How !

do you know a customer buys a product?"

How !

can you tell one customer story from another?"

How !

Completed Event Table!

Customer Transaction Type/Method Date/Month/Period

Product/Service Promotion/Reason Location/Store/Hospital

Event/Fact Employee/Organisation Time

How

Why

Who !

What!Where!

When !

When!When does it happen?!

Date!Time!Time Zone!Period!Timeline: Milestones!

How!How does it happen?!How do we know it happened?!How do we uniquely identify a fact/event?!

Activity, Process, Event!Effect, Outcome!Transaction Type!Transaction # [Degenerate Dimension]!Step #!

[Granularity, Event Type: Discrete, Evolving, or Recurring]!

Who!Who does what? How do we organize them?!How do they change? Who else is involved?!

Customer: Business, Consumer, Segment!Employee!Supplier!Partner!Third Party!

How Many!How many/much is involved? How long doe it take?!

Revenues!Costs!Quantities, Balances!Activity/Status Counts!Durations!

[UoM, Fact Type: Fully Additive, Semi-Additive, Non-Additive]!

Where!Where does it happen? Where doe it refer to?!

Location!Branch, Store, Facility, Channel!URL!Map: Start, Previous, Current, Next, Last!

What!What is involved/used? How are they organised?!How do they change? !

Value Proposition!Product!Service!Resource!

Why!Why does it happen? Can it be different? If so, why?!

Cause, Reason!Promotion, Deal!

The BI Model Canvas !

Agile Data Warehouse Design: www.modelstorming.com ! Inspired by The Business Model Canvas (www.businessmodelgeneration.com/canvas), this work is licensed"under a Creative Commons Attribution-ShareAlike 3.0 Unported License. 2012, Lawrence Corr!

Title, Author(s), Date/Version!

Next Steps!

infoq.com/minibooks/scrum-xp-from-the-trenches!

modelstorming.com!@LawrenceCorr!decisionone.co.uk!

Webinar eBook offer (30% off):!

gum.co/modelstorming/senturus!

Agile Dimensional Modeling & Data Warehouse Design Course "with Lawrence Corr "

19-20 August 2013, San Francisco Bay Area"

info.senturus.com/2013-08-19-Agile-Dimensional-Modeling-and-Data-Warehouse-Design.html!

$1,295!

More info…

Q&A