The requirements are best defined as user stories. They are described in the language of the customer. The customer's expectations of the product, service or process are described. For example, a user can search the product list via a search mask and gets a result. Technical details and processes are omitted. In a good User Story, the who, what, and why must be clarified. User Story's are described via a template: As a , I want so that / with it . In a User Story, the goal must be clearly communicated. As a user, I want to search for a customer ID so that a customer can be found faster. This representation helps the stack holders to better understand the need of the customer. The User Story is sorted by priority and story point. The priority is the importance and value of a User Story and the story point is the effort to implement a User Story. If User Stories are more extensive, they can be subdivided and assigned to an Epic. If a User Story is even more extensive, a theme is defined.