As a Developer
I want to understand how to capture content reqiurements quickly
So that I can estimate their size and obtain a priority for the order to deliver
Why document Information Products?
When starting an AgileBI project there is often a need to undertake a scope, size and prioritise phase before you can start the delivery phase.
If you are running a waterfall / Agile hybrid process, then you may need to do a project initiation or business case phase before you can start the delivery phase and for this, you need an estimate of the time it will take to deliver the “total” solution.
As part of this, you often have to do an estimate of the resources required to deliver or agree on the order in which you will deliver. The old “give me a dedicated team and 12 months and I’ll deliver your hearts desire” trust me approach is not so successful sometimes.
Of course, we don’t want to do Big Requirements Upfront. The challenge is how do you do enough work up front to be able to give confidence you can deliver but not spend months stocktaking the current environment or gathering masses of detailed requirements that will change before you start delivering.
One of the ways to do this is to create an Information Product Roadmap to articulate what might be delivered, and when, during the delivery phase. This gives confidence you have done enough work to have a high-level prioritisation and estimate of effort, and that you understand enough about the requirements to have some focus when you start building.
And once you start the delivery work, how do you get just enough requirements to develop in an iterative way, where change is ok because you haven’t spent a long time capturing and building to those requirements.
The AgileBI technique we use to manage these challenge is documenting requirements in an Information Product Template.
What is an Information Product?
To do this we use the concept of an Information Product. Information Products are a way of describing something that bounds together:
- The business outcome or benefit that will be achieved by using the Information Product;
- The business questions that will be answered by using the content;
- The data-driven business processes that are required by the users;
- The audience (persona’s) that will use it;
- The visualisations that might be delivered;
- The features the users will require.
Each of these are defined the way we define them in the delivery phase using our AgileBI techniques such as BEAM, Story boards and wireframes.
I often think of Information Products as apps on your smartphone, something you click on to achieve a task or outcome.
Where can I find an Information Product Template?
The Business Intelligence Information Product Template I use to define an Information Product can be found here:
When to create or update an Information Product Template?
Like a lot of the artefacts, we deliver in our AgilebI approach the Information Product template is updated multiple times as we progress through the process. Each time more detail is added to the template as we discover and document it.
There are four major stages where the Information Product template is updated:
The initial version of the Information Product template is created, with the minimal amount of detail required to allow prioritisation to be undertaken. It can also enable the product roadmap/backlog to be created and an initial High-Level estimate of effort for each Information product (in terms of number of sprints)
- Sprint Estimation
The Information Product template is updated with more detail to enable it to be included in a sprint. This is often done as part of the backlog refinement. The aim is to ensure it can be delivered within the sprint (or a number of sprints) that is expected.
- Build Design
The Information Product template is updated with enough detail to enable the dev team to start building. This is typically done at the beginning of the sprint process, in conjunction with the Vision, BEAM and wireframing workshops.
- As Built
The Information Product template is finally updated as an as-built document to confirm what the dev team delivered.
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,...
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...
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...
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...
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...
As a Product Owner or Developer I want I want to understand how a Minimum Viable Product relates to AgileBI So that I can deliver faster and safer One of the ways to deliver quickly is to focus on what is often termed in Agile as a “Minimum Viable Product...
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...
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...
As a AgileBI Coach
I want I want to understand how to determine if the AgileBI Team are in a healthy state
So that I can keep the sprint team engaged