User Stories

What is this method about?

A tool used in agile development that helps teams to view a system’s features and goals within the context of their different users. The tool organizes the features/goals according to the users that each one impacts and details how users interact with the system to achieve their goals.

Why use it

User stories provide insight into how different users are impacted by system design when trying to achieve their goals—aiding design and development teams in identifying who the various users are and how they can help those users to achieve their goals more easily.

When should I use it?

During the beginning stages of development and design—user stories often serve as a guideline for how we will proceed with both of these. It’s also a good idea to keep the user stories relevant and updated during all phases of design and development, continually providing a user-centered compass for what needs to be done throughout the design process.

What you get

• Teams will generate a list of user stories for inputting in to the product backlog. • User stories will form the scope of work for the agile team, with prioritized stories being allocated to each sprint.

At a glance

• Time: Short, Long
• Effort: Low
• Cost: Low

Materials

• Requirements List
• Features List
• Markers
• Whiteboard or workspace
• Sticky notes
• Software to note the user stories e.g. Excel or Confluence

Who is involved

• Product Manager
• Product Owner
• Design and development team representatives (possible)