User Stories: What Users Want, and Why
A User Story is a simple description of a feature from the user's perspective, focusing on the 'who, what, and why' instead of technical details. It's the primary unit of work in Agile, building a shared understanding of what to build.
The mental model
A User Story is not a technical requirement document. Think of it as a short story describing what a user wants to accomplish and why. It's a promise for a future conversation between developers, designers, and stakeholders to hash out the details. The focus is always on the value delivered to the end-user, not the implementation.
How it works
User Stories are typically written on index cards or in a digital tool, following a simple template: "As a [type of user], I want to [perform some action], so that [I can achieve some goal]." For example: "As a logged-in customer, I want to save items to a wishlist, so that I can purchase them later." This structure ensures the team understands the user (the "who"), the action (the "what"), and the motivation (the "why"). Stories are then prioritized in a product backlog.
When to use it
User Stories are the cornerstone of Agile development methodologies like Scrum and Kanban. They are ideal for defining features in a product backlog, planning work for an iteration or sprint, and fostering collaboration within a cross-functional team. They help keep the team focused on delivering user-centric value rather than just implementing technical tasks.
When not to use it
They are less suited for non-functional requirements like performance, security, or scalability, which often apply to the system as a whole rather than a specific user action. These are better captured as technical tasks or constraints. They are also not a substitute for a full requirements document in highly regulated industries where detailed, upfront specifications are legally mandated.
One canonical example
A team is building an e-commerce site. Instead of a task like "Build wishlist database table," they use a story: "As a shopper, I want to add a product to a wishlist, so that I don't forget it and can buy it later." This small story prompts conversations about how the wishlist should look, how many items it can hold, and how a user adds or removes items, ensuring the final feature actually meets the shopper's needs.
Interview question
What is the main purpose of a User Story in an Agile context?
- a.To serve as the final, unchangeable specification for a product feature
- b.To provide a comprehensive technical blueprint for a new feature
- c.To initiate a conversation about a user's need and the value it deliversCorrect
- d.To clearly define all system-wide non-functional requirements
Why? this is the answer
The card states a User Story is a "promise for a future conversation" focused on "value delivered to the end-user," not technical details. Its main purpose is to initiate discussion about a user's need and its value, rather than being a detailed technical specification.
Just read this? Test yourself on what you have been reading.
Read the original → agilealliance.org
- #agile
- #scrum
- #product management
- #user story
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on agile — each one lists the topics its interview covers.
See open roles