A user story is a short requirements description of a feature from an end user's perspective. It triggers the inner loop, where developers implement the change, while leaving further details for implementation discussion. section 2.1.1
Structure a story around three parts:
- Role: identify the stakeholder who benefits. section 2.1.1
- Feature: state the desired capability or behavior. section 2.1.1
- Benefit: explain why the capability is valuable. Keep the story independent, negotiable, valuable, estimable, small, and testable using the INVEST criteria. section 2.1.1
- Agree on acceptance criteria with stakeholders before implementation; use them to determine whether the requirement is complete. section 2.1.1
Appointment category selection
As a patient, I want to select an appointment category so that I can book the right kind of appointment for my medical needs. A matching acceptance scenario could require that selecting Cardiology shows only appointment options for that category.








