As a BI Practitioner
I want to understand what AgileBI is and how it differs to Agile
So that I know what approaches to use (and which approaches not to)

When deliverying new Data, Analytics or Content in an AgileBI you have the benfit of leveraging the majority of the Agile approaches that have been defined and refined over the many years the various Agile approaches have been around.

But some of these some of these Agile approaches need to be tailored when delivering Data, Analytics and Content.  This is typically due to the complexity that comes with data we do not create or control.  AgileBI delivery is different to the typical “APP” development where the developer has control of both the way data is captured and the way it is presented.

For example I have found that using three weeks as a sprint iteration is more effective than the standard two weeks.

The articles below provide more details on the differences and the recommended techniques for deliverying in an AgileBI way.

AgileBI Team Articles

Benevolent Dictator

As a AgileBI Guru I want to understand what a Benevolent Dictator is So that I know when one is needed   The team have discussed it "to death" and are now constantly repeating the same arguements "around and around" More informaiton is neded to progress...

Remote Scrum Masters

As a Stakeholder or Product Owner
I want some examples of things that can fail in AgileBI
So that I know what to watch out for

Coaching the Product Owner

[[make them succesfull]] [[make them safe]] [[teach them what they don't know]] [[guide them in the right direction]] [[dont do it for them]] [[dont let them abdicate]]

AgileBI Team

As a BI Practitioner I want to understand what an AgileBI team is and isn't So that I know how to form and storm one Building a self organising team is one of the key factors required to deliver in an AgileBI way. Creating a team with T-Skills and helping...

Retrospective – Transferring Team Maturity

[[moved form one project to new one]] [[started at the place i left off]] [[hadnt taken new team on the journey]] [[new team also picked up some things faster and other things slower than last team]] [[art is reading people]]

Agile Team Maturity

[[teams go at different paces]] [[have to learn as they go]] [[may have had bad experience with agile]] [[need to fail to fix]]  

6 + 2 = 4

We get taught during our life that 1 + 1 can equal three when we leverage the power of a team. This is often true and in AgileBI ... [[scrum teams deliver more]] [[velocity]] But [[adding people mod sprint makes every thign slower]] So at the beginning 6 + 2 will...

Other Blogs from this category

Adding members to the Agile Team makes you go slower

As a Stakeholder or Product Owner I want I want to understand if constantly adding Agile Team members is a good idea So that I can have a valid conversation with my Product Owner and Scrum Master Initially at least! VelocityWhen building a new AgileBI delivery team,...

Standups should be open not closed

As a Stakeholder or Product Owner I want I want to understand who can attend a standup So that I can ensure we are following an Agile approach Standups One of the many key things in deliverying in an AgileBI way is the use of daily standups to...

Remote Scrum Masters

As a Stakeholder or Product Owner
I want some examples of things that can fail in AgileBI
So that I know what to watch out for

No Meetings

As a BI Manager or Scrum Master
I want to understand how to deal with ‘meetings’ in an AgileBI project
So that I can change the team’s negative view on collaboration

AgileBI Discipline

As a BI Practitioner
I want to understand what AgileBI Disciplines are
So that I know what Disciplines to follow (and what Disciplines not to)

Making Retrospectives Fun

As a scrum master
I want I want to understand how to make retrospectives fun
So that I can keep the sprint team engaged

It’s Agile not Adhoc

There are a number of myths abound about the Agile approach. These include that idea that having a daily 15 minute standup is being Agile, to Agile doesn't deliver documentation. When I hear these myths I typically reply with "Agile is not Adhoc". So let's list the...

Other Blogs from this category

Three Agile Testing Methods – TDD, ATDD and BDD

As a Product Owner or Developer I want I want to understand the different Agile testing methods So that I can decide which to useIn the word of Agile, there are currently three methods that can be used to improve our testing practices and to assist with enabling...

Test Concerns

When talking about testing in a data project we have to first identify that the testing we need to do is similar but different to the testing we do in application development project. One of the useful way to identify these differences is to understand a number of the...

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 Danger of Pipelining and Time Slicing

As a BI Manager I want to understand the impact of pipelining the Agile teams workflow So that I know if it is an approach I wish to use Managing to complete an AgileBI build in three elapsed weeks is very very difficult. And by a build I mean from...

The Big Guess Up Front (BGUF)

As a Stakeholder or Product Owner
I want to understand where the traditional planning documents fit in the AgilebI process
So that I know when I need to have them created

Time boxing effort as acceptance criteria of last resort

As a Product Owner or Developer I want I want to understand how to deal with a lack of clear acceptance criteria So that I don't delay delivery Acceptance criteria for a user story is crucial.  Without it the development team and product owner...

AgileBI Process

As a BI Practitioner
I want to understand what AgileBI processes are
So that I know what processes to implement (and what processes not to)