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

Multiple Scrum teams

[[scrum of scrubs nope]] [[ two stand ups , inner and outer rings]] [[archutect sits on all planning sessions]]

Other Blogs from this category

Agile Discipline – Planning

There is a myth that Agile is all about being adhoc and that there is no planning upfront involved. It's not true. In fact when undertaking a AgileBI approach the team will spend far more time in planning sessions than in a typical waterfall project. What is different...

Agile Discipline – Documentation 

There is a myth that Agile doesn't deliver documentation.  It's not true. We always do the documentation that is required during a BI project, such as design and as built documents, what differs is the way we create them and when. A waterfall project is all about...

Other Blogs from this category

No Results Found

The page you requested could not be found. Try refining your search, or use the navigation above to locate the post.