User Story Basics
What is the standard format of a user story?
"As a [type of user], I want [goal], so that [benefit]".
Identify if this story is good or bad: "As a user, I want everything to work perfectly."
Bad – it's vague and doesn’t explain value
What is the purpose of acceptance criteria in a user story?
To define clear conditions under which the story is considered complete.
Name one Agile principle that supports writing user stories.
"Deliver working software frequently" or "Customer collaboration over contract negotiation."
What does the acronym INVEST stand for in the context of user stories?
Independent, Negotiable, Valuable, Estimable, Small, Testable
What makes this user story weak? "As a developer, I want to set up an API endpoint, so that I can connect to the database."
It’s too technical; it focuses on implementation instead of user value.
True or False? Acceptance criteria should be written in technical terms for developers.
False – they should be clear and understandable by everyone.
What does the “so that” part of a user story explain?
The value or benefit to the user.
Why should user stories be small?
To ensure they are easier to estimate, complete within a sprint, and deliver incremental value.
Is this a strong story? Why or why not? "As a customer, I want to filter products by category, so that I can find items faster."
Yes – it’s user-focused, valuable, and testable.
Give one example of acceptance criteria for this story: "As a user, I want to reset my password."
Example: The system sends a reset link to the user’s registered email when the "Forgot Password" button is clicked.
What Agile framework popularized user stories?
Scrum, though they are also used in XP and other frameworks.
Who is typically responsible for writing user stories?
Product Owners, though collaboration with the team is encouraged.
Rewrite this bad story into a better one: "As a user, I want a button, so that I can click on it."
"As a shopper, I want to add items to my cart with a button, so that I can purchase them."
Identify the missing acceptance criterion for this story: "As a customer, I want to add items to my cart."
"The cart updates the total price after an item is added." (or similar functional criteria).
Fill in the blanks: User stories are not about _______ features but about ________ value.
"building," "delivering."
True or False? User stories should always include technical details about implementation.
False! They should focus on the what and why, not the how.
What is missing in this story? "As an admin, I want to export user data."
The benefit or reason for exporting data is unclear.
Write two acceptance criteria for this story: "As a user, I want to search for products by name."
1. The search results display items matching the query.
2. If no matches are found, the system shows a "No Results" message.
What is a spike in Agile, and how does it relate to user stories?
A spike is a task designed to research or investigate a solution when details about a user story are unclear.