User stories are a simple schema to organize the PBI requirements around the end user's needs, motivations, and goals.
They keep the team focused on the value they create for the end-user and are written using the following format:
See examples of user stories to learn to write your own and explore the essential Scrum glossary.
By using user stories, you can say goodbye to the wasted time of working on the wrong thing.
They keep the team focused on the value they create for the end-user and are written using the following format:
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:
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
Here are 3 examples:
Checkout process functionality
Advertising campaign
Marketing campaign (Did you know you could use Scrum for marketing)
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.
Making an impact is hard
It’s easy to feel stuck or uncertain about how to move ahead. Maybe you feel overloaded or like you’re just spinning your wheels.
What if you had someone alongside you on the journey?