1 / 19

AGILE

AGILE. Does it work with Data Warehouses?. What is Agile BI?. The Agile Manifesto - 2001. “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

eara
Download Presentation

AGILE

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. AGILE Does it work with Data Warehouses?

  2. What is Agile BI?

  3. The Agile Manifesto - 2001 “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” Source: www.agilemanifesto.org

  4. 12 Agile Principles – Process • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. • Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. • Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. • Working software is the primary measure of progress.

  5. 12 Agile Principles - People • Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. • Business people and developers must work together daily throughout the project. • Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

  6. 12 Agile Principles - Other • The most efficient and effective method of conveying information is face-to-face conversation. • At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour. • Continuous attention to technical excellence and good design enhances agility. • Simplicity--the art of maximizing the amount of work not done--is essential. • The best architectures, requirements, and designs emerge from self-organizing teams.

  7. What people say about Agile For Agile: • Increases delivery speed • Decreases wasted effort • Deals with change • Fewer costly failures • More value delivered, faster and earlier Against Agile • No documentation • Lots of re-work • No time for architecture or design • Cowboy delivery • No “Big Picture” • Makes mistakes due to lake of planning • Doesn’t work in BI

  8. Suncorp An Agile Case Study

  9. What Suncorp did for Agile • Trained all IT staff and selected users in Agile delivery methodology • Removed Waterfall-based project funding • Showed commitment from CIO down • Developed communities of practice in Agile • Connected with partners better than us in Agile so that we could learn from them • Invested in infrastructure to support Agile • Built values and a culture around Agile

  10. What Agile means at Suncorp CONCEPT INITIATE DELIVER DEPLOY 5% 5% 5% 85% Stand-ups, Show-Cases, Retrospectives, Pair Programming, Adaptive Planning, Sustainable Pace, Auto Testing, Test Driven Development, Continuous Integration Practices Collaboration, Flexibility, Team Work, Business Value, Simplicity, & Speed Principles Trust, Innovation, Accountability, Courage, & Honesty Values

  11. Suncorp’s Agile BI System • Automated Testing • Continuous Integration • Agile-friendly ETL tools • User self-development areas • Fortnightly Iterations with showcases • Multi-location teams • Burn-up charts for progress monitoring

  12. Fortnightly Iterations Week 1 Week 2 ShowCase and Retro Iteration Planning Mtg Joint Development UAT and Signoff Backlog Expansion for next Iteration

  13. Details of the CI/Auto Testing When ETL code is changed and code packages are created, they are checked in to Subversion along with tests and CSV test data. Hudson CI Server monitors Subversion and initiates whenever changes are detected. Hudson starts a build comprising installation of new ETL package(s) to CI Schema and runs Concordion for automated testing If the build is successful, Hudson installs the ETL package(s) into the DevMasterschema for use. Hudson lights the Red or Green traffic lights to demonstrate results Data Devmaster Schema CI Package created Committed to Subversion ETL Tests

  14. Traps in Agile BI • Some documentation is needed, but not too much. • Not all developers like doing testing! • Need an Iteration 0 to set up architecture and platform first. • It’s all or nothing. Using waterfall underneath doesn’t work, as per the Half-Arsed Agile Manifesto

  15. Half Arsed Agile Manifesto We have heard about new ways of developing software by paying consultants and reading Gartner reports. Through this we have been told to value: • Individuals and interactions over processes and tools and we have mandatory processes and tools to control how those individuals interact • Working software over comprehensive documentation as long as that software is comprehensively documented • Customer collaboration over contract negotiation within the boundaries of strict contracts, of course, and subject to rigorous change control • Responding to change over following a plan provided a detailed plan is in place to respond to the change, and it is followed precisely That is, while the items on the left sound nice in theory, we’re an enterprise company, and there’s no way we’re letting go of the items on the right Source: www.halfarsedagilemanifesto.org

  16. Tips for Agile BI • In Iteration 0, do some initial architecture envisioning • Model the details just in time  • Prove the architecture early • Focus on usage • Organize your work by requirements in priority order • Ensure active stakeholder participation • Take an evolutionary approach • Test throughout the lifecycle • Involve operations and support people early • Adopt common development standards Source: adjusted from http://www.agiledata.org/essays/dataWarehousingBestPractices.html

  17. Is Agile BI the Holy Grail? Answer: NO

  18. What people say about Agile For Agile: • Increases delivery speed • Decreases wasted effort • Deals with change • Fewer costly failures • More value delivered, faster and earlier Against Agile • No documentation • Lots of re-work • No time for architecture or design • Cowboy delivery • No “Big Picture” • Makes mistakes due to lake of planning • Doesn’t work in BI ½  ½ ½ ½       

  19. Questions?

More Related