A user story is a short, non-technical statement of a product requirement written from the user’s point of view. A user story is usually written according to the following structure:
“As a ❮type of user❯, I want to ❮perform some task❯ so I can ❮achieve some goal.❯”
The Product Owner prioritizes the stories in the sprint backlog that are to be developed sprint during the sprint planning meeting. The team members assign story points to each story to estimate the effort needed to finish the individual stories, and break them down into tasks to be completed during the sprint. When the iteration or sprint is completed, the team should have produced a functional product or deliverable that corresponds to the initial requirement specified in the story.
=> Become a Certified ScrumMaster
=> Become a Certified Scrum Product Owner
=> How to calculate and work with a Velocity in Scrum
Scrum Academy GmbH
Sohrab is a long-standing Certified Scrum Trainer (CST) and CEO of the Scrum Academy GmbH based in Cologne. He is a trained medical doctor and worked for Bain & Company as a consultant and as a CIO at SE-Consulting, among others, before founding the Scrum Academy. As a consultant and trainer, he has been supporting companies from a wide range of industries for over a decade on topics related to agile transformation, innovation and organizational development.
Learn about DevOps in this article. From the challenges to the originals and goals of DevOps in an organization. More in our agile dictionary.
Find out what A/B Testing is all about and read more about the basics in our Agile Dictionary with some examples and tools to start your first A/B Test!
What does VUCA mean and why is it so important in this time? This article explains everything that you need to know about VUCA!