Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Better story writing


Here's a template that I've used to help me write stories, although never used in its entirety. Mostly to gather ideas and remind myself to think of criteria. Certainly want to build "Small user stories – easier realisation."

Do any of you use a "template" or similar strategy to write better stories?


h2. As who I want what so that why. or "Hierarchy > of the > item to address" (for example)

Which epic?
* Epics, or non-functional User Stories…

DoD (Definition of Done)

A good user story should be:
* "I" ndependent (of all others)
* "N" egotiable (not a specific contract for features)
* "V" aluable (or vertical)
* "E" stimable (to a good approximation)
* "S" mall (so as to fit within an iteration)
* "T" estable (in principle, even if there isn't a test for it yet)

And is it ready?

Common mistakes:

h3. Acceptance Criteria
* given…, when…, then…


h3. QA / Qualification
#* asdf
# Role
#* asdf
# Steps

h3. Regression potential
* Check…

h3. Assets
* asdf

h3. Documentation
* In Confluence…


Thank you!



Log in or Sign up to comment