User Stories and Requirements Analysis

User Stories and Requirements Analysis This task aims at creating a requirement specification for the project and it is performed in sync with Task 2.1. In contrast to most projects, those requirements will not be created in a plain textual report. Instead of this, it will focus on the user input and will be strongly driven by users by allowing them to define “User Stories”. This approach is derived from the SCRUM approach . SCRUM is an agile development approach, which allows user-centric definition of user stories within a so called “product backlog”. Each user story will define a very small part of the requirements definition and may be as small as one sentence saying “As a [role], I would like to [...]”, e.g. “As a site manager, I would like to be alerted in case of a sick leave”. The requirement specification and user stories are defined together users and professionals in focus groups and interview, applying different methods to obtain end-user feedback, such as card sorting techniques, story-telling, storyboarding, drawing and visual thinking, brainstorming, role playing, etc. The outcome of T2.3 will be a collection of those user stories and may contain several dozen user stories. Those stories will then be used as input for the architecture definition as well as the specifications which will derive concrete tasks and technical aspects from the user stories.