Way of Working

Capturing Requirements as stories and epics

20 November 2019 • 2 minutes

Written by Tessa Mylonas

Way of Working title image

How to write epics and stories to capture the requirements of a project.

The capturing of requirements enables the team to achieve a shared understanding of what needs to be built. A strategy for capturing these requirements is to understand the user intent through epics and user stories, which are then captured and maintained in a requirements backlog.



An epic is a high-level theme or feature that is used to categorise related stories.
An epic contains the following information:


A bicycle sharing app might include the following epic:
Summary: Browse bicycles
Description: View and filter nearby bicycles.
Personas: Users
Scope: When I want to find a bicycle to ride, I can see nearby bicycles and filter them based on my wants and needs.
Benefits: Users can view all available bicycles that suit their criteria and are walking distance from them.
Acceptance criteria:



A story is a fine-grained requirement, written from a user’s perspective. Each story belongs to only one epic. A story is the classification of tasks which are delivered during development, so they must be small enough to be completed within one iteration (i.e. you must be able to build it in less than 2 weeks).

A story contains the following information:


Within the \“Browse bicycles\” epic, there may be the following user story:
Summary: Filter bicycles
User story: As a user, I want to be able to filter nearby bicycles so I can find one that fits my criteria.
Background: This is how the user will locate bicycles that fit their specific criteria.
Acceptance criteria:

Implementation notes:

Helpful resources

Tessa Mylonas

Written by Tessa Mylonas

Head of Support and Education

If Tessa isn’t busy answering support questions or educating you about the Codebots products, she is typically found putting together flat-pack furniture, playing with her chocolate Labradors or hoarding houseplants.