As a Developer
I want to understand how to gather requirements
So that I can actually use them to deliver something of value
when deliverying using a Waterfall approach, big requirements up front are often done for months before any sort of build is undertaken by the team.
[[weak validation of business requirements]]
[[need repeatable process that can iteratively build out]]
[[need documetation that can be used for a certain task]]
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 member of a AgileBI team I want to understand how BEAM and Data Vault align So that I can leverage components from each at the right time Whether you are pipelining [[link]] your Agile delivery or you are managing to deliver...
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 technically...
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]]