Ingredients of a good user story

I have read and heard about people talking about what is a good story made of. Well in my point of view, a good story is one which the team defines as "Good". The whole idea of being agile, is to empower the team to differentiate what is good and what is bad. I definetly think that calling a story as "a good story" is a teams decission probably after having looked at a few bad ones :)


Nonetheless, there is no harm in knowing what people in the agile world are thinking of when they talk about the definition of a good story. Here is my take on the same - hope this helps:



Here are my 5 cents on the topic:

• Don’t elaborate be specific (Elevator-friendly)
• Size your stories well
• Prioritize them
• State the assumptions of the story and call them our clearly
• Flush out the right business value in the Acceptance criteria
• Validate story tasks against the acceptance criteria
• Avoid technical information in a functional story (Make it customer focused)
• Separate functional stories from tecnhnical stories/integration stories 
• Add additional data supporting your story  (wire frame, data, examples, etc)
• Get a analysis sign-off from the business before the team starts working on them