Scrum User Stories

They keep the team focused on the value they create for the end-user and are written using the following format:

• As a… [user]
• I want to… [goal]
• So that I can… [motivation] 

See examples of user stories to learn to write your own and explore the essential Scrum glossary.

‍

Acceptance criteria is written using the following structure:

• Given that [context allowing me to take an action]
• When [I take the action]
• Then [a result occurs indicating success or failure]

Learn more about how acceptance criteria is used in Scrum and explore the essential Scrum glossary.

A user story focuses on the identity, goals and motivations of the user you’re designing for. It emphasizes the why of the new functionality.

Acceptance Criteria focuses on the action taken by the user to meet their goal. It highlights the what of the new functionality.

See more acceptance criteria examples and learn to write acceptance criteria or learn other essential scrum terms.

Acceptance criteria is structured using the template

• Given that [context allowing me to take an action]
• When [I take the action]
• Then [a result occurs indicating success or failure]

Here are 3 examples:

Checkout process functionality

• Given that I’ve added all the items to my cart and I’m logged in,
• When I click the check out button,
• Then the checkout page loads with all my payment and shipping information preloaded.

Advertising campaign

• Given that someone fits our ideal customer persona,
• When they search for keywords we’re targeting,
• Then a link to a compelling offer is displayed above the fold.

Marketing campaign (Did you know you could use Scrum for marketing)

• Given that a customer is already receiving email communications,
• When they visit the site and engage content related to a specific product,
• Then they will be automatically subscribed to nurturing campaign highlighting that product. Or

See more acceptance criteria examples and learn to write how to create your own or learn other essential scrum terms.

‍

They aren’t absolute measurements like hours or days but measure the amount of work a PBI takes relative to other PBIs. Typical measurements include using Fibonacci numbers or t-shirt sizes.

Learn to use story points and explore the essential Scrum glossary.

In Scrum, you are not measuring work in absolute terms like hours spent or lines of code to be written. Two reasons for this:

1. Not everyone works at the same pace or has the same set of expertise and experience.
2. Until you do the job, these are unknown and, at best just guesses.

The problem with absolute sizing using hours is you begin to measure the people, not the work. Relative sizing measures the new work against past work shared by the whole team. Instead, the work is sized relative to past work already completed. So when looking at a new user story, the team asks, “Is this user story A most similar to this past user story B or this past user story C?”

Learn other essential Scrum terms.

The Fibonacci sequence is the go-to solution for many Scrum teams because it allows for relative sizing while still being a numeric measurement. It has two key advantages:

1. Keeping story points measured in numbers is advantageous because it is then easier to calculate a team's velocity.
2. The numbers have distinct relationship with each other making relative sizing more intuitive. The Fibonacci sequence increases such that each number is the sum of the previous two number.

Non-numeric options are still possible, and one of the most popular is using t-shirt sizing, like small, medium and large. Lean more about using story points or learn other essential Scrum terms.