User Stories Are Conversations, Not Contracts
A user story captures who needs what and why. It's a placeholder for a conversation between the product manager, designer, and engineer — not a detailed specification. The acceptance criteria define when the story is done.
INVEST Criteria
- Independent — can be developed without depending on other stories
- Negotiable — details are discussed, not dictated
- Valuable — delivers value to the user or business
- Estimable — the team can estimate the effort
- Small — fits within a single sprint
- Testable — has clear acceptance criteria
Key Takeaway
Good user stories are small, valuable, and testable. The acceptance criteria are what make them actionable.