Agile Methods and Data Warehousing

Agile Methods and Data Warehousing:
How to Deliver Faster
Kent Graziano
Data Warrior LLC
Twitter @KentGraziano

Agenda
 My Bio
 Why Agile & DW
 Agile Manifesto
 12 Agile Principles
 Agile Concepts
 Two weeks?
 Getting to Agile/RAD
 Data Vault
 Conclusion
(C) 2005-2014 Kent Graziano

My Bio
 Oracle ACE Director
 Certified Data Vault Master and DV 2.0 Architect
 Member: Boulder BI Brain Trust
 Data Architecture and Data Warehouse Specialist
● 30+ years in IT
● 25+ years of Oracle-related work
● 20+ years of data warehousing experience
 Co-Author of
● The Business of Data Vault Modeling
● The Data Model Resource Book (1st Edition)
 Past-President of ODTUG and Rocky Mountain Oracle
User Group

Why Agile & DW?
 Perceptions
● DW too slow to produce results
● DW projects “fail”
● DW projects fail to adapt to business changes
 Goal
● Change perceptions
● Deliver value
● Be more adaptable and flexible

Objectives
 Understand what is meant by “agile”
 Try to apply some agile ideas to data
warehouse and business intelligence efforts
 Answer the question – can we deliver results
faster?

Manifesto for Agile Software Development
http://agilemanifesto.org
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
Kent Beck
Mike Beedle
Arie van Bennekum
Alistair Cockburn
Ward Cunningham
Martin Fowler
James Grenning
Jim Highsmith
Andrew Hunt
Ron Jeffries
Jon Kern
Brian Marick
Robert C. Martin
Steve Mellor
Ken Schwaber
Jeff Sutherland
Dave Thomas
© 2001, the above authors
this declaration may be freely copied in any form,
but only in its entirety through this notice.

Principle #1
 Our highest priority is to satisfy the
customer through early and continuous
delivery of valuable software.
●Who is the customer?
●What is “valuable software” in data
warehousing?
● BI reports
● Dashboard interface
● Working ETL code?
● In the context of the customer!

Principle #2
 Welcome changing requirements, even
late in development. Agile processes
harness change for the customer's
competitive advantage.
● Must be flexible and adaptable in thinking and
design
● Use code generators (more on this later)
● Start with normalized models

Principle #3
 Deliver working software frequently,
from a couple of weeks to a couple of
months, with a preference to the
shorter timescale.
●Need good scope control!
●One subject area at a time
● What is a subject area?
●Think Data Vault (more on this later)

Principle #4
 Business people and developers
must work together daily throughout
the project.
● DW MUST have the business involved
● One of the Top 10 reasons for failure
● This applies for BI reports
● Daily interaction would be great!
● But – politics and priorities may interfere!
● At HP GBI/EDW – we used “war” room

Principle #5
 Build projects around motivated
individuals. Give them the environment
and support they need, and trust them to
get the job done.
● Need people who WANT to be on the project
● Get training if needed
● Keep units of work small to create an
atmosphere of success
● Don’t try a Big Bang EDW

Principle #6
 The most efficient and effective method of
conveying information to and within a
development team is face-to-face
conversation.
● Daily team huddles
● Co-located work space
● While face-to-face is efficient, still need some
documentation (or meta-data) for later
● Use a tool like JIRA

Principle #7
 Working software is the primary measure
of progress.
●Applied to DW:
● What is “working software?”
● BI reports
● Tables definitions and working ETL code
● Think more broadly – it is not just a data
entry screen

Principle #8
 Agile processes promote sustainable development. The
sponsors, developers, and users should be able to
maintain a constant pace indefinitely.
● DW Programs last a long time – don’t burn the team
out with unreasonable deadlines
● See P#5 – Motivated individuals
● Good planning and scope control
● No all nighters!
● Smallest valuable unit of work possible
● Keep it moving like a production line
● Pick (or develop) a standard, repeatable
methodology
● Study the Agile methods and adopt what works for your team
● Data Vault Modeling Methodology

Principle #9
 Continuous attention to technical
excellence and good design enhances
agility.
● Bad design + bad architecture = trouble
● Symptom: can’t build a requested data mart
● Frequent design reviews a must
● Improves team skills – provides cross training
● Over time – better designs, shorter review cycles
● Faster delivery

Principle #10
 Simplicity--the art of maximizing the
amount of work not done--is essential.
● KISS – Keep it Simple Stupid
● Write less code by hand
● Use code generators! (No syntax errors – ever)
● Oracle SDDM, Oracle Warehouse Builder
● ERWin
● AnalytxDS (for DV)
● WhereScape RED (also DV)
● Talend Open Profiler
● Modifications are easier – just regenerate the code

Principle #11
 The best architectures, requirements, and
designs emerge from self-organizing teams.
● Team of smart, motivated people = success
● We succeed (or fail) as a TEAM
● Don’t micro manage or pigeon-hole staff
● Encourage team work and team thinking
● Staff will gravitate to roles based on skills, interest,
and personality
● Then they have more buy-in to the process
● Eliminates delays and bottlenecks by having
shared responsibilities (no single point of failure)

Principle #12
 At regular intervals, the team reflects on how
to become more effective, then tunes and
adjusts its behavior accordingly.
● The Decision Model
● Debate Mode
● Check Points
● Related to self-organizing teams
● Make finding the solution to a problem the team’s
problem
● More buy-in to the solution
● Retrospectives are a MUST!

Decision Model in Action
Plan
Debate Decision

Check
Point
Questions
?
?
?
?
Answers
Mini-Debate
(Cause a
Slight Change
in Direction)
Iterate
Courtesy of Dr. Ed Freeman, CIO/CTO, Denver Public Schools

Agile Concepts for DW
 Team Huddles (Morning Scrum)
 Extreme Programming
 Pair Programming
 Domain Neutral Components
●Domain Archetypes

Team Huddles
 Daily Standup Meeting
● AKA Scum
● Morning Roll Call (FDD)
 Short meeting (< 15 minutes)
● Every morning, mandatory attendance
● Review assignments, accomplishments, backlogs
 Immediate feedback and assistance
● Keeps team motivated and on track (P #5)
● Identifies constraints and bottlenecks early in the
process
● Eliminates backlogs more quickly via re-assignments
 Improves team work
 Supports self-organizing teams (P #11)

Extreme Programming (XP)
 Programmer works directly with the end user
● At HP used Virtual Classroom or NetMeeting
 In DW:
● Best with developing BI reports
● DW or data mart must already be populated
● Reports developed using BI tool
● With the user in the room (or virtual)
● With constant user reviews and input using a web reporting tool
● Also applies to developing a dashboard or portal interface
● Works for ETL as well!
● Used war room with business to get near instant validation of
ETL changes

Pair Programming
 Part of XP
 Programmers work side-by-side
● One terminal
● One codes, the other reviews
● Two terminals, one cube
● One programming, one documenting
● Could also be done virtually!
 In DW:
● Writing ETL Code
● Pair data modeling

Two week iterations?
 Goal is really a few weeks to a few months
(see P#3)
 What is the deliverable?
● A fact table for a star schema
● A dimension table
● A complete star (fact and all dimensions)
● One piece of ETL code that populates a fact
table
● A function needed by the ETL code
● A new report or query
 Who is the customer?
● BI programmer?
● Knowledge worker?
● ETL programmer?

HP EDW Examples
 Business found missing report elements
 Solution: modify 3 tables to add 5 new columns in
reporting model (star schema)
 Tasks:
● Document requirements and ETL specs
● Modify Logical & Physical model (w/peer review)
● Rebuild tables in development
● Develop and test ETL
● MTI (Move To Integration) tables and code
● Execute and test ETL
● Modify report in UAT environment & test
 Result: Revised report ready in 18 hours, 44 minutes
● Less than 1 business day
 2nd case: 6 tables, 16 new columns
● Ready for UAT in 72 hours

Getting to Agile/RAD
 “better than average expertise”
● Expert consulting and mentoring
● Do the work (OTJ)
 At Denver Public Schools – took two years
before we could try being more “agile”
● Needed experience in DW, Oracle Designer, OWB,
and the “process” of building, deploying, and
maintaining and Oracle DW
 At HP GBI/EDW it took about a year
● Needed the right team and the right management
support
● Also the right project with willing business users
 At McKesson over a year so far setting standards
and training staff – but some success already

Data Vault – How it fits
 Data modeling technique for enterprise data
warehouse design
● See Data Vault white papers at www.danlinstedt.com
● The book: Super Charge Your Data Warehouse
 Allows modeling EDW in small chunks
● Develop model, build tables, build ETL, populate,
repeat (often)
● Key: prioritize the data requirements
● Think User Stories ala SCRUM

References
 Agile Management for Software Engineering:
Applying the Theory of Constraints for Business
Results by David J. Anderson
 CASE Method Fast-track: A RAD Approach by
Richard Barker & Dai Clegg
 The Goal by Eliyahu M. Goldratt
 The Business of Data Vault Modeling by Dan
Linstedt, Kent Graziano, & Hans Hultgren
 Super Charge Your Data Warehouse by Dan
Linstedt

Conclusion
 Agile concepts can be applied to data
warehouse and BI projects
● Not a purist definition!
● Try to apply the principles – be creative
 Suggested approaches
● Data Vault 2.0!
● Use team huddles
● Use universal models as template
● Use pair programming to increase quality and cross
training
● Use code generators like SDDM & OWB
● Use the Data Vault modeling approach
● Read about Agile Methods (XP & FDD)
● Read Oracle CASE Method Fast-Track
● Be flexible and give it a try

Super Charge Your Data Warehouse
Available on Amazon.com
Soft Cover or Kindle Format
Now also available in PDF at
LearnDataVault.com
Hint: Kent is the Technical
Editor

Data Vault References
www.learndatavault.com
www.danlinstedt.com
On YouTube:
www.youtube.com/LearnDataVault
On Facebook:
www.facebook.com/learndatavault

Agile Methods and Data Warehousing

Contact Information
Kent Graziano
The Oracle Data Warrior
Data Warrior LLC
Kent.graziano@att.net
Visit my blog at
http://kentgraziano.com

Agile Methods and Data Warehousing

More Related Content

Viewers also liked (8)

Similar to Agile Methods and Data Warehousing (20)

More from Kent Graziano (10)

Recently uploaded (20)

Agile Methods and Data Warehousing

Editor's Notes