... I prefer to take another approach. Incorporate data into each and every story. Think for a moment about the “T” in the popular INVEST acronym (a way to remember and assess what makes a good User Story). User stories are supposed to be Testable. We go to great ends to write unit, functional, and integration tests. But how about testing our basic hypotheses? Or that the story is meeting user expectations and driving the expected value? .... Accompanying Article: https://medium.com/@johnpcutler/user-stories-and-data-32057117fc7b#.w2yhspv12

5. Who uses …
“Standard” Format?
Acceptance Criteria?
Definition of Done?

7. As product
developers, what
leaves us with a sense
of impact?

10. In your organization,
when is a story done?

22. Example: GIVEN that people are perpetually in need of
social gratification WHEN they encounter a “feed” of
friend related news-snippets THEN they will spend
hours online, and may even click on ads.