AgileBI Requirements Workflow

by | 6.1 - Requirements, Backlogged, Process

As a BI Practitioner
I want to understand what order to gatther requirements
So that I can gather them efficiently

When coaching or mentoring a new AgileBI team on the AgileBI Way one of the first things they ask is what is the standard order in which to gather requirements?  Do we run BEAM workshops first or do we run the Information Product workshops?

There is no standard answer.

One of the awesome things about the AgileBI Way is you can use a lot of the techniques in any order you want.  You can effectively create your own AgileBI Way using these techniques as building blocks (I tend to think of them as Lego blocks) and combine them to create your own workflow (I tend to think of my own Lego tower).

AgileBI Requirements Techniques

There are a core number of AgileBI techniques that you can use to create your own workflows.  Some come from the reqiurements view, some from the engineering view.  These include:

  • Vision and Scope, Stakeholder Onion
  • Information Products
  • Data Requirements (BEAM)
  • Data Vault Modeling
  • Business Rules

Each of these techniques have different processes for capturing the reqiured information and different templates to capture this information in.  [thats what makes it cool]

Examples I have seen

Working with different teams across different customers I have seen different workflows emerge from each of them.  Often this is driven by the type of project that is being delivered.

Legacy System Replacement


[reverse enginerr the legacvy platform][new data build first][content only]


New Data Build


New Solution

[new thin slice]

New Content


Other requirement articles.

Information Products – Gather Size and Prioritise

  As a Developer I want to understand how to run the Information Products workshops So that I can deliver reqiurements quickly Information Products As outlined in the Information Product post there are four major stages where the Information Product template is...

Stakeholder Onion

As a product owner I want I want to understand how to identify my stakeholders So that I know who can tell me what to do and who to tell what we are doing Other Blogs from this category

Wireframing to confirm requirements

As a developer I want I want to understand how to use wireframing to confirm requirements So that I can build the right thing Wireframing is a technique we use to confirm two things: How does the user wish to see the content presented? Have we identified...

Gathering Data Requirements

As a scrum master I want I want to understand how to make retrospectives fun So that I can keep the sprint team engaged The Data Requirements Gap There are two typical challenges when we gather data requirements.  First, we capture and document the requirements in a...

Business Rule Templates

When do BI projects that require new data we know anecdotally that once we have acquired the required data from the System of Records the majority of our time and risk is applying code that transforms and/or augments data. In my terminology I call this "doing bad...

The death of the 100 page BI Strategy

The death of the 100 page BI Strategy

As a Stakeholder or Product Owner
I want to understand where the BI strategy fits into the AgileBI process
So that I know when I need to have it created

Agile Engineering

As a BI ManagerI want to understand what risk and challenges I will encounterSo that I know what I am getting myself into Reducing your delivery timeframe down to 3 weeks, means you need to find ways to automate many of the...



As a Developer
I want to understand how to gather requirements
So that I can actually use them to deliver something of value

BEAM meets Data Vault and wham bam thank you ma’am 

As a Developer I want to understand who I can leverage BEAM and Data Vault together So that I can develop faster and safer. Whether you are pipelining [[link]] your Agile delivery or you are managing to deliver a thin slice [[link]] every sprint iteration both should...