Updated: Jun 1
User stories are part of an agile approach that helps shift the focus from writing about requirements to talking about them. All agile user stories include a written sentence or two and, more importantly, a series of conversations about the desired functionality. (Mike Cohn, Mountain Goat Software)
Before we begin: Backlog grooming
To be ready for a User Story Workshop, you need a well maintained and groomed backlog.
What does this mean exactly?
removing user stories that no longer appear relevant
creating new user stories in response to newly discovered needs
re-assessing the relative priority of stories
assigning estimates to stories which have yet to receive one
correcting estimates in light of newly discovered information
splitting user stories which are a high priority but too coarse-grained to fit in an upcoming iteration
When is this done?
Usually 30 minutes once a sprint by the PO and any other interested parties. This is likely significantly higher at the start of a product increment/project.
Leading a User Story Elaboration workshop
AKA: User Story Review, User Story Requirements
Objectives of the session: Fundamentally create a shared understanding of each story across the team in order to draw on the collective mindset, transfer knowledge across the team and enable any team member to kick the story off.
When: Teams tend to do this twice weekly for 30 minutes, depending on the velocity of the team.
STEP 1: Bring User Stories
Select the next few stories for development based on priority and
bring them to the session.
Assigned to: PO
Draw this to a wall to review the stories, adding the first one for review:
Assigned to: PO/ Analyst
Step through each item, moving fast by time boxing discussions and parking items quickly to be problem solved offline. You should end up with something like the below. Note, if you have UX designs, bring them along for the discussion!
Assigned to: Anyone
Before moving onto the next story, look into the next steps:
Does the estimate need to be changed?
Are all of the questions owned or ready for whoever kicks off the story?
What tasks are needed to deliver this story? Do we need to card them up?
Do we need to touch base with any stakeholders?
Assigned to: Team