Introduction to Agile BI: Modifying agile methods for a BI project
Part 2 of 4
In part 2, we will look at modifying agile methods for a BI project. Read part 1 reviewing of the key differences between Agile and waterfall here. In later installments we will discuss converting a team to use agile methods and a brief introduction to some Agile Data Modeling concepts.
How is a BI project different than a typical agile OLTP project?
First we will take a look at the architecture of each.
Web Architecture BI Architecture
As you can see, there are more pieces. Multiple sources, repositories, downstream databases, and applications that increase the complexity. This can be broken down into the Breadth and Depth of Complexity. Breadth includes extracting, cleansing, integrating, and transforming. While depth includes conflicting data definitions, business rules, and high data volumes.
Creating another layer of requests under user stories
These are developer stories. If the user story is being able to view sales by product type and region over time. You may need to break this down behind the scenes and have tasks for product, customer, geography and sales data loads.
Adding additional team roles (A person may fill more than one role.)