A user story is a request which is formulated in everyday language or business language to a computer program in a maximum of two sentences. The user story plays an important role in agile software development, which makes it easier for the customer to formulate tasks for the software or programmers.
The origin of user stories go back to 1998. At that time, customers requested to be able to formulate the goal of a project in simpler terms in the framework of extreme programming. User stories were to be formulated in the same way as application cases. The most important aspect was the practical aspect, which allows customers to formulate requirements without using programming languages. Today, user stories are an integral part of agile software development.
In 2001, Ron Jeffries developed the three Cs formula of the creation of user stories, consisting of card, conversation, and confirmation:
With regard to a Scrum, the product owner is responsible for creating user stories.
In this way, the stakeholder can precisely formulate or negotiate the requirements of an agile software.
A user story is usually developed according to a fixed structure: User type -> Action -> Goal or "As a <role>, I want <goal/desire> so that <benefit>"
Name: Export all top 10 rankings of a subpage as a CSV file Description: I would want to download this data to create a history of my rankings.