Yuriy SimonoffSenior Project Manager| N/ABuffalo Grove, Il, United States
All user stories for agile are focused on application development. But I'm working on datawarehosue implementation. Does anyone have good user story samples related to such area? As there are interdependent activities that do span time and usually in excess of single sprint. Saving Changes...
Sort By:
George FreemanThought Leader | Author | Architect| Florida, United States
"Agile Data Warehousing" by Ralph Hughes has some good advice and some example stories. I'm assuming your mission is actually not to implement a DW, but to provide some specific reports, analysis and decision support capabilities to users. I mention that obvious point only because a common cause of failure with such initiatives is that they start by saying "let's build a DW". Hope this helps. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
You do not need user stories for data warehouse. Data warehouse is a matter of architecture. User stories could be used just in a componente inside the data warehouse architecture which is the layers where data is used, which today is called "data science" or "data analysis" (I know, both are not the same thing). For the other components you do not need user stories. Saving Changes...
User stories are simply one method of starting a conversation about requirements. If they don't fit the scope of your project, nothing prevents you from using a different requirements modeling technique. Never use a practice where it doesn't fit.
If you are using a backlog-based agile delivery approach, the contents of the backlog will usually be a mix of work items - new features (expressed as stories or other requirements constructs), defects, knowledge capture work, experiments, spikes and so on...
