If you ever show me a “user story” in the form of “As a user, I want to _ so that I can _” here are some of the questions I’m going to ask, so we might as well figure out the answers up front so we can skip to a set of much more interesting questions that will come later:
What we call a User Story isn't a spec, it's a formatted reminder to have a bunch of interesting conversations later on. It's the barest of beginnings. Thanks for reminding us again about this!
Daniel Markham
Replying to and
It's a fair question but (I believe) your underlying assumptions are invalid, ie, that there is some kind of point in time where all conversations will happen for X. Think of conversations as dynamic and continuous, not fixed boxes to check off.
Given the same User Story, different teams will need differing amounts of discussion. Also, hopefully, some discussions can resolve issues for multiple stories. It is a non-predictable thing. If we knew the answer to that, we wouldn't need US to begin with. We'd just write specs.
One more piece of info. For folks who like that US title format, the reason it works well is that what we need is an acceptance test. This format helps us get there. We have convos until we know enough to have a test, then we write code to pass the test.

Trending now

What’s happening

Last night
Bill Gates owns less than 1% of farmland in the US, fact-checkers report
May The 4th Be With You
Promoted by Obi-Wan Kenobi
Rihanna Reacts To Marble Statue The Met Gala Made In Her Honor ⁠— Complete With Baby Bump
Elite Daily
May 2, 2022
Ashley Tisdale Just Won The Met Gala, & She Wasn't Even There
Entertainment · Trending
Dave Chappelle