Why do we need Agile Analytics?

What is Agile Analytics?

Agile Analytics is not a rigid or prescriptive methodology; rather it is a style of building a data warehouse, data marts, business intelligence applications, and analytics applications that focuses on the early and continuous delivery of business value throughout the development lifecycle.


The Agile Manifesto is adapted to make it more appropriate to Agile Analytics by Ken Collier:


Manifesto for Agile Analytics Development:

Individuals and interactions over processes and tools

Working DW/BI systems over comprehensive documentation

End-user and stakeholder collaboration over contract negotiation

Responding to change over following a plan


The items on the left are valued more than the items on the right.


How does Agile Analytics work?

Waterfall vs Agile

  1. Iterative, incremental, evolutionary: Agile is an iterative, incremental, and evolutionary style of development. The system is built in short iterations that are generally one to three weeks long by adapting to frequent user feedback.
  2. Value-driven development: Every iteration must produce at least one new user-valued feature.
  3. Production quality: Each newly developed feature must be fully tested and debugged during the development iteration and acceptable by the user.
  4. Barely enough processes: Traditional styles of DW/BI development require “signing off” formalities in transition from requirements analysis to design. Primary objective is the production of high-quality, high value, working systems, the amount of ceremony required for other activities are minimized.
  5. Automation: The only way to be truly Agile is to automate as many routine processes as possible. The more automation is done, the more focus is on developing user features.
  6. Collaboration: In traditional projects, the development team solely bears the burden of meeting timelines, budgets and quality. In Agile methodology, the project community includes the sub communities of users, business owners, stakeholders, executive sponsors, technical experts, project managers, and others. Frequent interaction between the technical and user communities is critical to success.
  7. Self-organizing, self-managing teams: The Agile project manager’s role is to enable team members to facilitate a high degree of collaboration with users another members of the project community. The Agile project team itself decides how much work it can complete during an iteration and then holds itself accountable to honor those commitments.



Why is Agile Analytics better than the Waterfall model?


Waterfall Methodology

Agile Methodology

  •   The software development process is classified into different phases in the Waterfall model.
  •   Agile methodology classifies the project development lifecycle into sprints.
  •   The development requirements need to be clear beforehand as there is no scope of changing the requirements once the project development starts.
  •   The Agile methodology is quite flexible as it allows changes to be made in the project development, even after the initial planning has been completed.
  •  In Waterfall methodology, the “Testing” phase comes after the “Build” phase.



  • In the Agile methodology, testing is performed concurrently with programming or in the same iteration as programming.
  •   The Waterfall model strictly lays its focus on the completion of project development.



  •  Agile methodology ensures that the developed product satisfies its end customers and changes itself as the requirements of customers change.


Agile methodology stresses on ensuring that the end customer is highly satisfied with the developed product and is flexible to accommodate the changes as the requirements of customers change even at a later stage.


References: Agile Analytics: A Value-Driven Approach to Business Intelligence and Data Warehousing by Ken Collier


Leave a Reply

Your email address will not be published. Required fields are marked *