User stories

In Scrum, we define requirements from the business in a unified format called “User stories”. The format of these stories benefit both the stakeholders and the team. For the stakeholder, it’s super easy to write a request for a new feature without taking technical aspects into account. From the teams point of view, it’s really easy to identify the request from the business and then plan the technical side of it.

The user story format is being described as follows:

As a <role>, I want <feature> so that <value>

User stories should be written in short format and the author of the story should take into consideration that it should be possible for the team to resolve it (one user story) during a normal workday.