Simple, clear, short description of customer valued functionality. 3 C’s: Card, Conversation, Confirmation. Represents customer requirements.
Priority: Title: As a [type of user], I can [goal] so that [value] Notes: Assumptions: Constraints: Estimate:
Checkout Using Credit Card 25 As a book shopper, I can checkout using my credit card so that I can purchase a selected book. Notes: Support mc, visa, amex Constraint: Must use Chase payment service 13 pts
Given [context] When [some event] Then [outcome]
Checkout Using Credit Card Test with valid mc, visa, amex passes Test with valid other cards fails Test with expired card fails Test with invalid cvv fails Test with invalid zip fails
Priority: Title: As a [type of user], I can [goal] so that [reason] Notes: Assumptions: Constraints: Estimate:
Title: Priority: As a [type of user], I can [goal] so that [reason] Notes: Assumptions: Estimate: Constraints: “Get smaller cards”
How do I describe what I want? How do I schedule this work and track its progress? How do I validate that this work is done? What are the details of what I need to code?
Estimate and Priority
Why Use User Stories?
Other Options The system shall… Use Cases
User Role Modeling
As a forgetful user, I can reset my password so that I can access my account.
As a customer support manager, I can automate password resets so that I can reduce support calls.
Questions? Independent Negotiable Valuable Estimatable Small Testable