Getting the Runs on the Board  One Run at a Time <ul><li>Business intelligence initiatives  </li></ul><ul><li>Ralph Kimbal...
Getting the Runs on the Board  One Run at a Time <ul><li>Two to three month sprints  </li></ul><ul><li>Extensive data ware...
Getting the Runs on the Board  One Run at a Time <ul><li>Focusing on user needs </li></ul><ul><li>Delivering as rapidly as...
OR <ul><li>Agile Business Intelligence </li></ul><ul><li>Lean mean business intelligence team </li></ul>Business Intellige...
Supporting Processes <ul><li>Source Control </li></ul><ul><li>Infrastructure Control </li></ul><ul><li>Automagical Testing...
Manifesto for Agile Software Development  <ul><li>Individuals and interactions  over processes and tools </li></ul><ul><li...
What Agile Isn’t <ul><li>Lack of processes and tools </li></ul><ul><li>Lack of documentation </li></ul><ul><li>Lack of con...
What Else Agile Isn’t <ul><li>A religious dogma </li></ul><ul><li>The difference between a methodologist and a terrorist i...
Which Agile Method Do We Use? <ul><li>Agile Unified Process (AUP)? </li></ul><ul><li>Agile Data Method? </li></ul><ul><li>...
Which Agile Method Do We Use? <ul><li>We haven’t chosen a methodology </li></ul><ul><li>Principle and practices that exper...
Lean Software Development <ul><li>I’m personally a fan of Mary Poppendieck’s work which is based on Toyota’s lean manufact...
Minimal Documentation <ul><li>Design Documentation </li></ul><ul><li>Handover Documentation </li></ul><ul><li>Change Manag...
Stage 1 – SET and SEC Model Our First Star Schema – SET and SEC Business Intelligence, Planning, Budgeting & Reporting
Stage 2 – Student Model Plus Live Student Feed Business Intelligence, Planning, Budgeting & Reporting
Stage 3 – GDS Model Plus Graduate Destination Survey Business Intelligence, Planning, Budgeting & Reporting
Stage 4 – At Risk Students, Staff, Admissions Models Plus Students at Risk, Staff, QTAC Feed Business Intelligence, Planni...
Documentation <ul><li>Data Warehouse Framework – Warehouse Architect </li></ul><ul><li>User Requirements – Business Analys...
Agile Still Needs <ul><li>Planning </li></ul><ul><li>Design Documents </li></ul><ul><li>Good Architecture and Design </li>...
Manifesto for Agile Software Development  <ul><li>Individuals and interactions  over processes and tools </li></ul><ul><li...
Agile BI Absolutely Needs <ul><li>Individuals and interactions  </li></ul><ul><ul><li>Talented well trained staff </li></u...
Good Design <ul><li>As an architect you design for the present; with an awareness of the past; for a future which is essen...
Good Design - Willis Faber & Dumas Headquarters <ul><li>The country headquarters for insurance company Willis Faber & Duma...
Good Design - 30 St Mary Axe – The Gherkin <ul><li>Built on the site of the Baltic Exchange Building </li></ul><ul><li>Her...
Good Design - Millau Viaduct - Southern France Business Intelligence, Planning, Budgeting & Reporting
Good Design - Millennium Bridge (London) Business Intelligence, Planning, Budgeting & Reporting
Good Design - Millennium Bridge (London) <ul><li>Opened June 2000  </li></ul><ul><li>£18.2m (£2.2m over budget) </li></ul>...
Design Patterns <ul><li>A design pattern is a formal way of documenting successful solutions to problems.  </li></ul><ul><...
Design Patterns – Pattern 21 Four-Story Limit <ul><li>Pattern 21 Four-Story Limit </li></ul><ul><li>May be part of Magic o...
Pattern Language <ul><li>Pattern Language (Wikipedia) </li></ul><ul><ul><li>Noticing and naming the common problems in a f...
Design Patterns Are Not <ul><li>One off Problems </li></ul><ul><li>Usable only in one business </li></ul><ul><li>Specific ...
Software Design Patterns <ul><li>October 1994 (2005 Copyright notice) </li></ul><ul><li>Design Patterns: Elements of Reusa...
Example Design Pattern - Singleton <ul><li>Used to restrict instantiation of a class to one object (What is that in Englis...
Dimensional Modelling Design Patterns <ul><ul><li>Dimension Design Patterns </li></ul></ul><ul><ul><li>Role Playing Dimens...
Fact Table Patterns <ul><li>The Kimball method uses  only three fact table  design patterns </li></ul><ul><ul><li>Transact...
Summary <ul><li>Agile works if </li></ul><ul><ul><li>Staff are talented, well trained, well funded and appreciated </li></...
References <ul><li>Lean software development : an agile toolkit / Mary Poppendieck, Tom Poppendieck.  Author: Poppendieck,...
Questions? <ul><li>Contact Details </li></ul><ul><ul><li>Telephone (07) 373 54052 </li></ul></ul><ul><ul><li>Mobile  0408 ...
Upcoming SlideShare
Loading in …5
×

Getting The Runs On The Board One Run At A Time V5

683 views
618 views

Published on

AAIR Data Warehousing (DW) Special Interest Group (SIG) Forum 2009 27-28 August, 2009, Griffith University, Nathan campus

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
683
On SlideShare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Getting The Runs On The Board One Run At A Time V5

  1. 1. Getting the Runs on the Board One Run at a Time <ul><li>Business intelligence initiatives </li></ul><ul><li>Ralph Kimball’s dimensional modelling design patterns. </li></ul>Business Intelligence, Planning, Budgeting & Reporting
  2. 2. Getting the Runs on the Board One Run at a Time <ul><li>Two to three month sprints </li></ul><ul><li>Extensive data warehouse, one data mart at a time </li></ul>Business Intelligence, Planning, Budgeting & Reporting
  3. 3. Getting the Runs on the Board One Run at a Time <ul><li>Focusing on user needs </li></ul><ul><li>Delivering as rapidly as possible </li></ul>Business Intelligence, Planning, Budgeting & Reporting
  4. 4. OR <ul><li>Agile Business Intelligence </li></ul><ul><li>Lean mean business intelligence team </li></ul>Business Intelligence, Planning, Budgeting & Reporting
  5. 5. Supporting Processes <ul><li>Source Control </li></ul><ul><li>Infrastructure Control </li></ul><ul><li>Automagical Testing </li></ul><ul><li>Bug Tracking </li></ul>Business Intelligence, Planning, Budgeting & Reporting
  6. 6. Manifesto for Agile Software Development <ul><li>Individuals and interactions over processes and tools </li></ul><ul><li>Working software over comprehensive documentation </li></ul><ul><li>Customer collaboration over contract negotiation </li></ul><ul><li>Responding to change over following a plan </li></ul><ul><li>That is, while there is value in the items on the right, we value the items on the left more </li></ul><ul><ul><li>http:// agilemanifesto.org / </li></ul></ul>Business Intelligence, Planning, Budgeting & Reporting
  7. 7. What Agile Isn’t <ul><li>Lack of processes and tools </li></ul><ul><li>Lack of documentation </li></ul><ul><li>Lack of contract negotiation </li></ul><ul><li>Lack of planning </li></ul>Business Intelligence, Planning, Budgeting & Reporting
  8. 8. What Else Agile Isn’t <ul><li>A religious dogma </li></ul><ul><li>The difference between a methodologist and a terrorist is that you can negotiate with a terrorist - Ralph Kimball </li></ul>Business Intelligence, Planning, Budgeting & Reporting
  9. 9. Which Agile Method Do We Use? <ul><li>Agile Unified Process (AUP)? </li></ul><ul><li>Agile Data Method? </li></ul><ul><li>DSDM? </li></ul><ul><li>Essential Unified Process (EssUP)? </li></ul><ul><li>Extreme programming (XP)? </li></ul><ul><li>Feature Driven Development (FDD)? </li></ul><ul><li>Getting Real? </li></ul><ul><li>Open Unified Process (OpenUP)? </li></ul><ul><li>Scrum? </li></ul><ul><li>Lean software development? </li></ul><ul><li>Crystal Clear </li></ul>Business Intelligence, Planning, Budgeting & Reporting
  10. 10. Which Agile Method Do We Use? <ul><li>We haven’t chosen a methodology </li></ul><ul><li>Principle and practices that experience shows as working </li></ul>Business Intelligence, Planning, Budgeting & Reporting
  11. 11. Lean Software Development <ul><li>I’m personally a fan of Mary Poppendieck’s work which is based on Toyota’s lean manufacturing </li></ul><ul><ul><li>Eliminate waste </li></ul></ul><ul><ul><li>Amplify learning </li></ul></ul><ul><ul><li>Decide as late as possible </li></ul></ul><ul><ul><li>Deliver as fast as possible </li></ul></ul><ul><ul><li>Empower the team </li></ul></ul><ul><ul><li>Build integrity in </li></ul></ul><ul><ul><li>See the whole </li></ul></ul>Business Intelligence, Planning, Budgeting & Reporting
  12. 12. Minimal Documentation <ul><li>Design Documentation </li></ul><ul><li>Handover Documentation </li></ul><ul><li>Change Management Documentation </li></ul><ul><ul><li>(Technical How To Documents and End User Documentation) </li></ul></ul>Business Intelligence, Planning, Budgeting & Reporting
  13. 13. Stage 1 – SET and SEC Model Our First Star Schema – SET and SEC Business Intelligence, Planning, Budgeting & Reporting
  14. 14. Stage 2 – Student Model Plus Live Student Feed Business Intelligence, Planning, Budgeting & Reporting
  15. 15. Stage 3 – GDS Model Plus Graduate Destination Survey Business Intelligence, Planning, Budgeting & Reporting
  16. 16. Stage 4 – At Risk Students, Staff, Admissions Models Plus Students at Risk, Staff, QTAC Feed Business Intelligence, Planning, Budgeting & Reporting
  17. 17. Documentation <ul><li>Data Warehouse Framework – Warehouse Architect </li></ul><ul><li>User Requirements – Business Analysts </li></ul><ul><li>Star Schema Design – Business Systems Analyst </li></ul><ul><li>ETL Jobs – Intern/Business Systems Analyst </li></ul><ul><li>Initiatives Support – Business Systems Analyst </li></ul><ul><li>Training Documents – BI Trainer  </li></ul><ul><li>How To Documents – All </li></ul>Business Intelligence, Planning, Budgeting & Reporting
  18. 18. Agile Still Needs <ul><li>Planning </li></ul><ul><li>Design Documents </li></ul><ul><li>Good Architecture and Design </li></ul><ul><li>Source Control </li></ul><ul><li>Migration Control </li></ul><ul><li>Managed Infrastructure </li></ul><ul><li>Testing++ </li></ul><ul><li>Handover and Training Documents </li></ul>Business Intelligence, Planning, Budgeting & Reporting
  19. 19. Manifesto for Agile Software Development <ul><li>Individuals and interactions over processes and tools </li></ul><ul><li>Working software over comprehensive documentation </li></ul><ul><li>Customer collaboration over contract negotiation </li></ul><ul><li>Responding to change over following a plan </li></ul><ul><ul><li>http://agilemanifesto.org/ </li></ul></ul>Business Intelligence, Planning, Budgeting & Reporting
  20. 20. Agile BI Absolutely Needs <ul><li>Individuals and interactions </li></ul><ul><ul><li>Talented well trained staff </li></ul></ul><ul><li>Working software </li></ul><ul><ul><li>Good Testing </li></ul></ul><ul><ul><li>Automagical where possible </li></ul></ul><ul><li>Frequent customer collaboration and interaction </li></ul><ul><ul><li>Engage the end users </li></ul></ul><ul><li>Responding to change </li></ul><ul><ul><li>Tools and data models that allow for adaptability </li></ul></ul><ul><ul><li>It’s hard to be adaptable when the tools are old </li></ul></ul>Business Intelligence, Planning, Budgeting & Reporting
  21. 21. Good Design <ul><li>As an architect you design for the present; with an awareness of the past; for a future which is essentially unknown – </li></ul><ul><ul><li>Norman Foster Jan 2007 Munich Germany </li></ul></ul><ul><li>http:// www.ted.com/talks/norman_foster_s_green_agenda.html </li></ul><ul><li>Note: Photos about Norman Foster from Wikipedia or www.fosterandpartners.com </li></ul>Business Intelligence, Planning, Budgeting & Reporting
  22. 22. Good Design - Willis Faber & Dumas Headquarters <ul><li>The country headquarters for insurance company Willis Faber & Dumas was a pioneering example of energy-conscious design that challenged accepted thinking about the office building. Offering a new social dimension with its swimming pool, roof-top garden and restaurant, it was conceived in the spirit of democratising the workplace and engendering a sense of community. </li></ul><ul><li>http://www.fosterandpartners.com/Projects/0102/Default.aspx </li></ul><ul><li>Constructed 1970 to 1975 </li></ul><ul><li>Open plan, three floors,1300 office staff </li></ul><ul><li>Listed by British Heritage as a Grade 1 building of outstanding architectural or historic interest. </li></ul>Business Intelligence, Planning, Budgeting & Reporting
  23. 23. Good Design - 30 St Mary Axe – The Gherkin <ul><li>Built on the site of the Baltic Exchange Building </li></ul><ul><li>Heritage listed building damaged beyond repair by a PIRA bomb in April 1992 </li></ul><ul><li>London’s first ecological tall building ... is rooted in a radical approach - technically, architecturally, socially and spatially. Generated by a radial plan, its energy-conscious enclosure resolves walls and roof into a continuous triangulated skin, allowing column-free floor space, light and views. http://www.fosterandpartners.com/Projects/1004/Default.aspx </li></ul>Business Intelligence, Planning, Budgeting & Reporting
  24. 24. Good Design - Millau Viaduct - Southern France Business Intelligence, Planning, Budgeting & Reporting
  25. 25. Good Design - Millennium Bridge (London) Business Intelligence, Planning, Budgeting & Reporting
  26. 26. Good Design - Millennium Bridge (London) <ul><li>Opened June 2000 </li></ul><ul><li>£18.2m (£2.2m over budget) </li></ul><ul><li>Closed 3 days later due to wobbling </li></ul><ul><li>People walking caused the bridge to sway in step </li></ul><ul><li>Retrofitted with 89 dampers to control movement </li></ul><ul><li>Reopened February 2002 </li></ul><ul><li>Retrofit cost £5m </li></ul><ul><li>Romans first bridged Thames in 50AD  </li></ul><ul><li>Medieval London Bridge lasted from 13th to 19th Century </li></ul><ul><li>Harry Potter and the Half Blood Prince </li></ul>Business Intelligence, Planning, Budgeting & Reporting
  27. 27. Design Patterns <ul><li>A design pattern is a formal way of documenting successful solutions to problems. </li></ul><ul><li>The idea was introduced by the Austrian born American architect Christopher Alexander and has been adapted for various other disciplines. </li></ul><ul><li>Christopher Alexander is Professor Emeritus at the University of California (Berkeley) </li></ul><ul><li>Alexander, Christopher et al (1977). A Pattern Language: Towns, Buildings, Construction </li></ul><ul><li>This book contains 253 Architectural Design Patterns e.g. </li></ul><ul><ul><ul><li>146. Flexible Office Space </li></ul></ul></ul><ul><ul><ul><li>147. Communal Eating </li></ul></ul></ul><ul><ul><ul><li>148. Small Work Groups </li></ul></ul></ul><ul><ul><ul><li>149. Reception Welcomes You </li></ul></ul></ul><ul><ul><ul><li>150. A place to Wait </li></ul></ul></ul><ul><ul><ul><li>151. Small Meeting Rooms </li></ul></ul></ul><ul><ul><ul><li>152. Half-Private Office </li></ul></ul></ul><ul><ul><ul><ul><li>( http:// downlode.org/Etext/Patterns / ) </li></ul></ul></ul></ul>Business Intelligence, Planning, Budgeting & Reporting
  28. 28. Design Patterns – Pattern 21 Four-Story Limit <ul><li>Pattern 21 Four-Story Limit </li></ul><ul><li>May be part of Magic of the City (10), City Country Fingers (3), Lace of Country Streets (5) </li></ul><ul><li>Conflict </li></ul><ul><li>There is abundant evidence to show that high buildings make people crazy </li></ul><ul><li>Resolution </li></ul><ul><li>In any urban area, no matter how dense, keep the majority of buildings for stories high or less. It is possible that certain buildings should exceed this limit, but they should never be buildings for human habitation May contain Number of Stories (96), Density Rings (29), Building Complex (95), Housing Hill (39), High Places (62) </li></ul><ul><ul><li>http://downlode.org/Etext/Patterns/ptn21.html </li></ul></ul>Business Intelligence, Planning, Budgeting & Reporting
  29. 29. Pattern Language <ul><li>Pattern Language (Wikipedia) </li></ul><ul><ul><li>Noticing and naming the common problems in a field of interest, </li></ul></ul><ul><ul><li>Describing the key characteristics of effective solutions for meeting some stated goal, </li></ul></ul><ul><ul><li>Helping the designer move from problem to problem in a logical way, and </li></ul></ul><ul><ul><li>Allowing for many different paths through the design process. </li></ul></ul><ul><ul><ul><li>( http:// en.wikipedia.org/wiki/Pattern_language ) </li></ul></ul></ul>Business Intelligence, Planning, Budgeting & Reporting
  30. 30. Design Patterns Are Not <ul><li>One off Problems </li></ul><ul><li>Usable only in one business </li></ul><ul><li>Specific to a location, state or country </li></ul><ul><li>One off business problems with a very specific set of parameters can be solved elegantly and simply but that is not a design pattern </li></ul>Business Intelligence, Planning, Budgeting & Reporting
  31. 31. Software Design Patterns <ul><li>October 1994 (2005 Copyright notice) </li></ul><ul><li>Design Patterns: Elements of Reusable Object-Oriented Software </li></ul><ul><ul><li>Software engineering book describing recurring solutions to common problems in software design </li></ul></ul><ul><ul><li>Written by Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides (The Gang of Four – None were married to Chairman Mao) </li></ul></ul><ul><ul><li>The book goes through common generic software engineering problems and discusses solutions to the problems in Object Oriented terms </li></ul></ul><ul><ul><li>Gives a common vocabulary to fairly abstract terms </li></ul></ul>Business Intelligence, Planning, Budgeting & Reporting
  32. 32. Example Design Pattern - Singleton <ul><li>Used to restrict instantiation of a class to one object (What is that in English???) </li></ul><ul><ul><li>For example, my software wants to connect to an Oracle database, but we only connect once; we would create the database connection as a singleton. If it exists at run time we use the one that exists, if not we create one. </li></ul></ul><ul><li>Prior to GOF’s book we described this in English but now we just say, “Use a singleton on the Oracle connection”. </li></ul><ul><li>Singleton is the simplest pattern (IMHO). </li></ul>Business Intelligence, Planning, Budgeting & Reporting
  33. 33. Dimensional Modelling Design Patterns <ul><ul><li>Dimension Design Patterns </li></ul></ul><ul><ul><li>Role Playing Dimension </li></ul></ul><ul><ul><li>Slowly Changing Dimensions (Type 1, Type 2, Type 3, Type 6 / Hybrid) </li></ul></ul><ul><ul><li>Audit Dimension </li></ul></ul><ul><ul><li>Ragged Hierarchies using Bridge Tables </li></ul></ul><ul><ul><li>Etc </li></ul></ul>Business Intelligence, Planning, Budgeting & Reporting
  34. 34. Fact Table Patterns <ul><li>The Kimball method uses only three fact table design patterns </li></ul><ul><ul><li>Transactional Fact Table </li></ul></ul><ul><ul><li>Periodic Snapshot Fact Table </li></ul></ul><ul><ul><li>Accumulating Snapshot Fact Table </li></ul></ul><ul><li>Fundamental Grains - Almost all data warehouses sit on one of three bedrock designs ( www.intelligententerprise.com/db_area/archives/1999/993003/warehouse.shtml ) </li></ul><ul><li>In Auckland 2007 he used stronger words than this, he said something like: “After looking at thousands of designs and being the chief architect on more than 30 enterprise data warehouse projects, I have yet to see a design that couldn’t fit into one of these three fact table grains”. </li></ul>Business Intelligence, Planning, Budgeting & Reporting
  35. 35. Summary <ul><li>Agile works if </li></ul><ul><ul><li>Staff are talented, well trained, well funded and appreciated </li></ul></ul><ul><ul><li>Software is well tested, delivered rapidly </li></ul></ul><ul><ul><li>Customers are engaged, interaction, regarded as capable </li></ul></ul><ul><ul><li>Software can rapidly adapt to change </li></ul></ul><ul><li>Agile Requires </li></ul><ul><ul><li>Good design (i.e. easily extendable) </li></ul></ul><ul><ul><li>Source Control </li></ul></ul><ul><ul><li>Infrastructure Control </li></ul></ul><ul><ul><li>Automagical Testing </li></ul></ul><ul><ul><li>Bug Tracking </li></ul></ul><ul><li>Dimensional Design Patterns </li></ul><ul><ul><li>Common vocabulary </li></ul></ul><ul><ul><li>Solutions to common design problems are available </li></ul></ul><ul><ul><li>Training and peer groups available </li></ul></ul>Business Intelligence, Planning, Budgeting & Reporting
  36. 36. References <ul><li>Lean software development : an agile toolkit / Mary Poppendieck, Tom Poppendieck. Author: Poppendieck, Mary. Publication: Boston : Addison-Wesley, c2003. </li></ul><ul><li>Norman Foster's Green Agenda http:// www.ted.com/talks/norman_foster_s_green_agenda.html </li></ul><ul><li>Alexander, Christopher et al (1977). A Pattern Language: Towns, Buildings, Construction. Oxford University Press, USA, 1216. ISBN 0195019199. </li></ul><ul><li>Gamma, Erich; Richard Helm, Ralph Johnson, and John Vlissides (1995). Design Patterns: Elements of Reusable Object-Oriented Software. Addison-Wesley. ISBN 0-201-63361-2. </li></ul><ul><li>http:// www.ralphkimball.com / </li></ul><ul><li>Ralph Kimball, Margy Ross, Warren Thornthwaite, Joy Mundy, Bob Becker The Data Warehouse Lifecycle Toolkit, 2nd Edition: Practical Techniques for Building Data Warehouse and Business Intelligence Systems John Wiley & Sons, 2008 </li></ul>Business Intelligence, Planning, Budgeting & Reporting
  37. 37. Questions? <ul><li>Contact Details </li></ul><ul><ul><li>Telephone (07) 373 54052 </li></ul></ul><ul><ul><li>Mobile 0408 074 082 </li></ul></ul><ul><ul><li>Email Address [email_address] </li></ul></ul><ul><ul><li>Facebook [email_address] </li></ul></ul>Business Intelligence, Planning, Budgeting & Reporting

×