User Story
A concise statement of the value a specific user will gain from a deliverable, serving as a commitment to discuss and clarify the details through conversation.
Key Points
- Captures value from the user's perspective and is kept small and focused.
- Often written as: "As a [role], I want [feature], so that [benefit]".
- Functions as a placeholder for conversation; specifics are refined collaboratively.
- Acceptance criteria define Done and guide estimation, testing, and planning.
Example
As an online banking customer, I want to set travel notices so that my card is not declined while I am abroad. The product owner and team will discuss details such as notice duration, destinations, and security verification, then define acceptance criteria (e.g., notices can be added, edited, expire automatically, and trigger a confirmation email).
PMP Example Question
Which statement best describes a user story in an Agile project?
- A comprehensive requirements document that fully specifies system behavior.
- A short, user-centered description of value that invites a follow-up conversation to clarify details.
- A technical task list used by developers to break down work.
- A summary of lessons learned captured during the sprint retrospective.
Correct Answer: B — Short, value-focused description that prompts conversation
Explanation: A user story highlights user value and serves as a reminder to collaborate on the details, not a complete specification or task list.
