4.5.1 Collaborative User Story Writing Flashcards
A user story represents a feature that will be valuable to either a “ “ or “ “ of a s…
user
purchaser
system or software.
User stories have 3 critical aspects (3 Cs):
- Card - the “ “ describing a … (an i… an entry in an e…
- Conversation - explains how the “ “ will be “ “ (can be d…
- Confirmation - the a…
- Card - medium
user story
index card,
electronic board) - Conversation - software
used
documented or verbal) - Confirmation - acceptance criteria
Most common format for a user story is:
“As a “ “, I want [goal to be “ “, so that I can [resulting business value f…”, followed by a…
[role],
[accomplished],
[for the role],”
acceptance criteria.
Collaborative authorship of the user story can use techniques like “ “ and m…
brainstorming
mind mapping.
The collaboration allows the team to obtain a shared vision of w… by taking into account 3 perspectives:
- b…
- d…
- t…
what should be delivered
- business
- development
- testing
Good user stories should be (INVEST):
- i…
- n…
- v…
- e…
- s…
- t…
- Independent
- Negotiable
- Valuable
- Estimable
- Small
- Testable
If a stakeholder doesn’t know how to test a user story, this may indicate that the u… is not c… , or that it doesn’t reflect something v… , or that the “ “ just needs help in “ “.
user story
clear enough
valuable to them
stakeholder
testing.