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
As outlined in the Information Product post there are four major stages where the Information Product template is updated:
- Gather, Size & Prioritise
- Backlog Refinement
- Build Design
- As Built
The gather, size and prioritise stage is when we create the initial version of the Information Product template, with the minimal amount of detail required.
This stage allows the team to size the effort reqiured to ba high-level estimate of effort to build the IP to be t-shirt sized and then the IP’s to be prioritised. It can also euilnable the product roadmap/backlog to be created.
The goal of the gather step is to quickly identify each of the Information Products that need to be delivered. Effectively taking a stock take of all the Information Products that may need to be delivered.
[may need beam]
[5 lanes][left and right., #1][done by product owner and support crew, SME, BA, Analyst][may need product owner of product owner sessions]
Other requirement articles.
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
As a Developer I want to understand how to document business rules So that we can increase the speed of delivery Another of the more difficult capabilities in data warehousing is the definition and...
One of the more challenging areas in Business Intellegence and Data Warehousing is understanding how to apply tests to data that has been transformed, to prove we have delivered a correct result. It can be as simple as proving that we are presenting the right revenue,...
With the death of the 100 page Business Intellgience strategy how do you get your stakeholders to come on the journey and agree to invest in the time for your AgileBI to create new data and content for them. With a waterfall project the process is well know, you do...
As a Developer I want to understand when and how to understand the source data So that I can be sure I can build the things in the users stories and as an input to the estimate of the effort required Often the majority of the AgileBI team are...
As a BI Practitioner I want to understand how to set expectations and limit the scope of a set of iterations So that I have some boundaries which means we will not have endless iterations or additions to requirements, without agreeing these changes upfront [[...
[[why you need to do it]] [[stakeholder onion]] [[surprise stakeholders and their new requirements]] [[identifying who should be keep informed]]