The sections of the document
| Section | What goes in it |
|---|---|
| Goal | The problem we solve and for whom, in three lines |
| Users and roles | Customer, staff, manager, and what each one sees |
| User stories | 'As a receptionist I want to record an appointment so that bookings never clash' |
| Acceptance criteria | What must happen for a story to count as done |
| Data | What is stored: customers, orders, products, and the fields of each |
| Out of scope | What we deliberately leave for a later version |
How to write it
- 1Write out a full working day
What happens from the first order until the till is closed? That is the source of every story.
- 2Turn it into short stories
One story per action, in the form: who, what they want, and why.
- 3Add an acceptance criterion to each
A sentence that can be checked with yes or no.
- 4Order by priority
What the business cannot run without comes first; the rest comes later.
- 5Show it to the people who will use it
Staff know details the manager does not.
What is the difference between an SRS and a PRD?
A product requirements document, or PRD, focuses on what we build, why and for whom. An SRS is more detailed and technical, and is usually asked for in contracts and tenders. A small project is fine with one document that covers both.