User Stories vs Data Stories

Agile is used to remove uncertainty from projects, so that the features for development are fairly clear, at least for the current iteration. However, producing an analytics application creates many more tasks because it is focused on data. To remove uncertainty from these data tasks, and the overall project, we keep it separate from development. This ensures that we: i) understand the data, ii) have a clear methodology for addressing problems using the data.

When the Data Stories are complete, we can be sure that software development using User Stories will proceed with minimal risk, as is typical of Agile projects.

User Story (development)​

  • Smallest unit of work in Agile framework​
  • Strict format for describing a software feature: ​
  • “As a [persona], I [want to], [so that].”​
  • Focused on the user​
  • Open-ended problem for creativity and collaboration​

​ Data Story (pre-plan, data exploration)​

  • An independent unit of analysis that scopes the dataset explored​
  • Informal framework for exploring data​
  • More problem-focused than general EDA, but not part of app development​
  • Removes uncertainty from data and solution methodology​