User story template

[gary-rowe]

In order to "some reason or business value"
As a "type of user"
I want "some feature"

Estimated time (days): 0.5, 1, 2, 3, 5, ?

---

Acceptance Criteria

Scenario 1: Title
Given [context]
And [some more context]...
When [event]
Then [outcome]
And [another outcome]...

---

When discussing, remember INVEST:

• Independent – a user story should not be dependent upon another story.
• Negotiable – the details of the story will be worked out during the conversation. Talk about the story before working on it.
• Valuable – the user story needs to be valuable to someone.
• Estimable – the estimation need not be perfect, but good enough so you can rank and schedule a story.
• Small – small is easier to estimate. Label as Small: 0.5-1, Medium: 2-3, Large 5+.
• Testable – make sure that you can validate the user story is done using automated tests.

See the Extreme Programming notes.