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 BI PractitionerI want to understand what order to gatther requirementsSo that I can gather them efficientlyWhen coaching or mentoring a new AgileBI team on the AgileBI Way one of the first things they ask is what is the standard order in which to gather...
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 category
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 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...
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 Stakeholder or Product Owner
I want to understand where the BI strategy fits into the AgileBI process
So that I know when I need to have it created
As a Developer
I want to understand how to gather requirements
So that I can actually use them to deliver something of value
As a Developer I want to understand who I can leverage BEAM and Data Vault together So that I can develop faster and safer. Whether you are pipelining [[link]] your Agile delivery or you are managing to deliver a thin slice [[link]] every sprint iteration both should...
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