You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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)
* 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? https://www.leadingagile.com/2015/07/definition-of-ready/
Common mistakes: https://www.scrumalliance.org/community/articles/2011/august/5-common-mistakes-we-make-writing-user-stories
h3. Acceptance Criteria
* given…, when…, then…
h3. QA / Qualification
h3. Regression potential
* In Confluence…