Specifications
What your team receives: tickets ready to build.
Here is an example of a user story, written the way I write them for clients. A need voiced in a meeting becomes an epic, then user stories, then tickets that each carry their acceptance criteria. A developer who opens the ticket knows what to build and how to check it is finished.
User storyPRD-142Example
As an operations manager, I want to export the month's customer requests, so that I can prepare the monthly review without re-entering data.
Acceptance criteria
- Given a selected month, when I run the export, then the file contains all the requests for the period.
- When no request exists for the period, a message says so and no empty file is produced.
- The export only contains the requests the user is allowed to see.
Out of scope
PDF export, automatic sending by email.
- The specification
- The project's reference document: the problem, the users, what is included and what isn't. Written in Linear, the project tracking tool, next to the tickets that implement it.
- The epic
- A coherent set of features, tied to a goal. It is used to prioritise and track progress without getting lost in the detail of the tickets.
- The user story
- A need expressed from the point of view of the person who has it: who, what, why. Every feature must be traceable to a real use.
- The acceptance criteria
- The verifiable conditions that say a ticket is finished. Developers use them to build, testers to check, and you to approve.