Agile BI/DW

Daniel Fagerströmwww.danielfagerstrom.com

Just follow the book?

• Yes, but …

• What are the user stories?• Agile DB practices?• Agile operations?

Dimension model

Customernamecity

Customernamecity

Storenameregion

Storenameregion

Productnameclass

Productnameclass

Dateyear

month

Dateyear

month

ReceiptLineamount

ReceiptLineamount

ArchitectureCustomer registry

Product registry

Org. registry

Transactions

Raw data Staging Dimension model

Marts

OLAP Cube Reporting

Applications

ETLETL

Backlog

• Start with the most important:– Star– Dimension– Attributes in the dimension

• ETL – start with simpler tasks:– One time load– Subset data

Breadth or depth

• Breadth– Simplified load of the most important dimension

modelsEarly feedback, earlier build of dependent

systems

• Depth– Complete load of one dimension at a timeEarly deployment of usable sub systems

Agile DB Practices

• Agile DB refactoring– Scott Ambler– Change scripts for everything

• Common code owner ship– Everybody can change the models– DB projects in MS VS DB professional

• Don’t become a bottle neck– Broad contact area between team members and

operations and source data specialists

Agile DB Practices

• Course architecture• Agile modeling• Just in time design• Agile documentation

Agile DB Practices

• Subset data • Your own DB and development sandbox• Staged deployment: dev test prod• Continuous deployment• TDD?

Agile Operations

• Involve operations from day one• Operations part of the project• Deploy at demo/production server often• Start source data deliveries ASAP

Conclusion

• Some mental barrier for DB/DW/BI-developers

• Transparent• Steerable• Works great!• Happy customers!

More at my blog:www.danielfagerstrom.com