Once you know what to build, the team needs to understand it. Requirements describe what a product or feature must do, and user stories are a simple way to write them from the point of view of the person who will use it.
You'll start with the basics of writing user stories and acceptance criteria, then see how epics, features, and user stories fit together. Next you'll learn how to write clear acceptance criteria that tell everyone when a story is done, and finish with a walkthrough of writing a product requirements document (PRD).
With clear requirements in hand, you'll be ready to work closely with developers in Agile & Working with Engineering, the next module in this course.
A worked example of how to write a user story and its acceptance criteria, and the mistakes teams often make when documenting them.
How epics, features, and user stories work together, and how big pieces of work are broken down into stories a team can build.
How to write acceptance criteria that are clear, testable, and understood by everyone on the team.
A step-by-step guide to writing a product requirements document that keeps product, design, and engineering on the same page.