User Story Creation Flashcards
Define how a user story is used
A user story helps translate technical requirements into easy-to-understand ideas.
User stories are stories about users.
User stories are simple descriptions of a feature told from the user’s point of view.
Identify the parts of a user story
Who - From whose perspective (aka user persona) will this user story be written?
What - What goal will be accomplished or implemented as the result of the user story?
Why - Why does the user need the functionality or feature outlined in the user story?
Highlight the importance of establishing an acceptance criteria.
Acceptance criteria are a set of statements, each with a clear pass/fail result, added to a user story.
Benefit multiple stages and stakeholders of a project, including:
Clarifying the scope for the project team
Assisting the development/implementation team
Ensuring testers know what should be tested
Acceptance criteria can also be formatted as if/then statements.
Summarize the INVEST concept to writing a user story.
Independent: User stories should be independent and not overlapping in concept with another user story.
Negotiable: A story is an invitation to a conversation. It captures the essence, not the details.
Valuable: The user story needs to be useful to the end-user. If a story does not have value, it should not be created.
Estimable: A successful user story’s timeline can be estimated, but just enough to help prioritize and schedule the story’s development/implementation.
Small: Smaller user stories tend to get more accurate timeline estimates. Remember, the details can be elaborated through conversations.
Testable: “Yes, I understand this user story so well that I can write acceptance criteria for it.”
Identify common mistakes to avoid when writing a user story.
The project team didn’t engage in story writing.
The who of the user story is an undefined user.
The why in the user story is feature-specific.
The acceptance criteria are too vague.
The user story was assigned to the implementation team without a team discussion.
