This picture was found on Flickr under the Creative Commons license. Thank you, Jose Hidalgo for the great picture.
User stories are a staple of Agile practices. Most teams use the following standard three-clause template:
As a USER
I want FUNCTIONALITY
So that BENEFIT
Teams are generally successful at creating conversation around user stories following the prescribed format, especially if they add acceptance criteria and adhere to the (3Cs) (Card, Conversation, Confirmation). Many teams also work hard to endow their stories with the INVEST qualities. Using the template, the 3 Cs, and infusing with INVEST, create sufficient user stories. Passing. Maybe even a B. But how do you get to an A+ and does it really matter?