Description
Cross-functional groups write user stories for the same epic from two contrasting personas, then derive test tasks, making user diversity tangible in the backlog.
Agile user stories often name a generic 'user', which hides who the product serves. In this workshop, groups mixing business, UX and ideally development staff each receive two personas chosen to be as different as possible. They write stories for one epic first from one persona's perspective, then from the other's, in the form 'As [persona, role], I want to... in order to...', and note test tasks for the stories. Plenary discussion compares the two sets. In the Danish experiments the diversity of users became tangible, managers' involvement built buy-in, proto-personas prompted participants to question the data, while detailed personas were trusted even where thin.
Attributes
- Discipline
- Design & Product Practice
- Loss type
- Latent
- Stage
- Definition
- Data
- Qualitative
- Effort
- Hours
Steps
- Form cross-functional groups of business, UX and development staff.
- Give each group two maximally contrasting personas and one epic.
- Write user stories for the epic from the first persona's perspective.
- Write stories for the same epic from the second persona's perspective.
- Derive test tasks for the stories.
- Compare the two story sets in group and plenary discussion and carry differences into the backlog.
Sources
- Persona Focused User Design (Nielsen, 2019)
Also known as
- Persona-driven user stories
- Persona user story workshop for agile teams
Categories
- Design
- Design & Product Practice