Coursya originals · Free PDF ebook

How to Write User Stories and Acceptance Criteria

Write user stories and acceptance criteria with a complete class-cancellation example, Given-When-Then scenarios, exceptions, story splitting and quality checks.

Agile, Scrum & Kanban

Write user stories and acceptance criteria with a complete class-cancellation example, Given-When-Then scenarios, exceptions, story splitting and quality checks.

The studio follows a small user need through conversation, criteria, delivery and verification. It includes consistent sample data, an ownership condition and a repeated-action scenario so the behaviour is testable.

Start with a user need

A story helps the team discuss a valuable change, not merely fill in a sentence template. A role label should point to a recognisable need. Use a concise form that leaves room for the right conversation. The short card is a reminder to clarify the behaviour and its limits.

Can an attendee cancel after a cutoff? What happens when the class is already cancelled? How is the capacity updated, and what evidence confirms the change?

Write acceptance criteria

Criteria make the relevant conditions observable and testable. A scenario should connect context, action and observable consequence. Make the first scenario concrete before adding exceptions. The ordinary path does not define every important boundary.

An attempted cancellation after the agreed cutoff follows the authorised rule and does not silently restore capacity. A missing booking produces an understandable outcome under the service’s policy.

Check permissions and repeated actions

A result should remain correct under relevant ownership and repetition conditions. Some requirements cut across the immediate happy path. A useful story is small, valuable and understandable enough to work on. A small story should still support a meaningful outcome.

Start with eligible single-place cancellations, then handle a separate group-booking case if needed. Each slice needs complete behaviour and relevant quality.

Connect stories with delivery and tests

Traceability helps the team preserve the need while the solution evolves. Readiness for work comes from understanding, not only a checklist status. A small wording change can alter several behaviours. The team should be able to explain, demonstrate and verify the intended change.

Do criteria show observable results with clear starting conditions, relevant exceptions and shared quality expectations? Are the numbers and state changes consistent?

Contents

  1. Start with a user need
  2. Identify the real user and outcome
  3. Write the first story
  4. Have the conversation
  5. Write acceptance criteria
  6. Use Given-When-Then where useful
  7. A complete happy-path example
  8. Explore exceptions deliberately
  9. Check permissions and repeated actions
  10. Include relevant quality conditions
  11. Review story quality
  12. Split into usable slices
  13. Connect stories with delivery and tests
  14. Refine with the right people
  15. Work a change in the rule
  16. Your story-and-criteria desk check

Using the PDF

Each numbered page contains an explanation, an original worked situation and a practical action. The bookmarks navigate the learning pages. A templates advertisement follows content page 5 and a Coursera Plus advertisement follows content page 15. The entire advertisement image is linked. Promotional links may earn Coursya a commission. A purchase is optional.

Frequently asked questions

Who is this guide for?

Write user stories and acceptance criteria with a complete class-cancellation example, Given-When-Then scenarios, exceptions, story splitting and quality checks.

How can I practise the ideas?

Follow the running case, work through the page actions and use the PDF bookmarks to revisit a topic. The final learning pages help you apply the decisions to your own project.

What does the download contain?

The PDF contains 19 pages, including 16 numbered learning pages, a cover and two linked advertisements. The book is written in English.

Share this article