Why are user stories too coarse for planning data integration projects?
What techniques can we use to discover our project’s “developer stories?”
How can we tell if we have a good developer story?
After amassing an initial project backlog of user stories, as presented in the prior chapter, data warehousing teams with a significant amount of data integration work will still not have a list of work items that fit nicely into the small time-boxed development iterations of Scrum. One further level of decomposition between Scrum’s user story and development tasks is necessary. Calling this intermediate requirements device a “developer story” indicates its conceptual position halfway between a user ...