What makes for good user stories? How do we get our teams to write good user stories? In this article, the author suggests that stories answer a simple set of questions: Who? Why? What? If the story is too complicated (or too vague) to answer those questions, it probably still needs more design from the Product Owner/team. Somewhere between being too large to manage (i.e. needing epic decomposition), and being too vague for the developer to actively design/code the story, lies the simple truth of these easy questions. What works for some, may not work for others.
