Just a Recommendation…how we Organize our Information Requirements
Information is required by business users throughout the industry. However, as part of our consulting engagements, we also encounter a lack of proper description as to what the business user actually needs.
So, we want to use this article to present the way we structure our information requirements internally at Scalefree as well as the way we do so for many of our customers.
What about User Stories?
We all know user stories from Scrum and many business intelligence projects.
Their structure is typically something that looks like:
As a <type of user>, I want <some goal> so that <some reason>.
The following example represents a typical user story we would receive in a project:
As a <marketing user>, I want <to have an overview report with the number of leads from a marketing channel> so that <I can adjust the marketing budget accordingly>.
Now, what should we do with this user story?
Many details are missing, and yes, we all know about product backlog refinement. The problem is that the user story is just not sufficient enough within business intelligence efforts and some structure might be of help.
Developers in enterprise data warehousing and business intelligence need much more detail than just the user story. On the other hand, the user story is a good starting point for the information requirement. So, it can be treated as a typical introduction. The overall structure looks like this: