A User Story has three primary components, each of which begin with the letter ‘C’:
As a [user role] of the product,
I can [action]
So that [benefit].
The collaborative conversation facilitated by the Product Owner which involves all stakeholders and the team.
The Product Owner must confirm that the story is complete before it can be considered “done”. The team and the Product Owner check the “doneness” of each story in light of the Team’s current definition of “done”
The test for determining whether or not a story is well understood and ready for the team to begin working on it is the INVEST acronym:
I – Independent
N – Negotiable
V – Valuable
E – Estimable
S – Small
T – Testable
Article concludes with tips on Splitting User Stories & Personas.
Author = Travis Birch (Berteig)