P I L O T
User Stories

1. Start from the user

Start identifying the users who will use the product/service and the purpose they would be using it for. You can go back to the Personas and select the ones which apply to the Pilot .

2. Create Epics

Epics describe the key functionalities of the product without going deep in the details. The pilot features, listed in the last exercice, will generate Epics. Write down each Epic using the user story template.

You need to associate a Persona and define what is the outcome and benefit of that feature to the user. Once you have all the Epics you can start detailing them into User Stories.

3. Refine Epics into User Stories

Break the epics into smaller stories using the INVEST model - each story needs to be Independent, Negotiable, Valuable, Estimable, Small and Testable.

4. Visualize & Communicate

• Make sure all user stories are visible and accessible for each stakeholder of the project.

• Effectively name, categorize and assign them to epics, themes and initiatives for easier navigation and administration.

5. Define Acceptance Criteria

Acceptance criteria outline the boundaries of user stories. They are used to confirm when a story is completed and working as intended. They are a set of conditions a user story should satisfy to be considered as done.

To make the acceptance criteria more comprehensive, include criteria on Functionality, Usability/User Experience, Error Handling, Performance and Stress Tests where applicable. A well written acceptance criteria will not only help in accurate planning and estimation but also serves as a basis for user testing and quality assurance (QA) testing.