Scrum components: Sprints & User Stories
Sprints last two weeks. A sprint is nothing more than a iteration .
Each sprint includes a meeting for planning, the implementation of the defined requirements and a meeting in which looking back on what has been achieved. This is followed by the planning of the next sprint at.
The basis for planning and implementation are User Stories . The requirements are there Fixed user view («As a visitor, I want a login button to log in.»)
Before the implementation, the team estimates the complexity of each story ( Estimation ). This forms the Basis for sprint planning.
Sprint process
- Before the sprint, we plan the content and scope together: the team estimates the complexity of the user stories and you determine what should be implemented.
- During the implementation, the team discusses completed and upcoming tasks on the daily. The Scrum Board shows the progress.
- At the end of the sprint, we present the completed stories - as an executable, interactive product. Together we look back on the sprint: What went well, how can we improve cooperation?
Product Owner
This is you or someone on your team. It is important that the person can and wants to make decisions. The Product Owner prioritizes the tasks and requirements and represents the product to everyone Stakeholders - including us.
Product Owner Assistant
Product Owner Assistant is someone from our team. In addition to moderator between the development team and the product Owner is also the contact person for all stakeholders.
Scrum Master
The Scrum Master ensures that everyone in the team can work efficiently. To the Tasks include removing blockages and obstacles of all kinds, in the team and externally convey and ensure that all important people are seated at the table.
Implementation team
Wasn't there yet ... Ah, exactly! The implementation team is provided by xoredge and is interdisciplinary: Design, development and testing. It brings all the necessary know-how for the successful implementation of the Project with.
Story Points & Estimation
Story points describe the complexity of each story (and not the time it takes). The Estimation is usually carried out in the form of a planning poker : All received a set of cards with the values 1 - 2 - 3 - 5 - 8 -… (Fibonacci series) and show your estimate at the same time. at deviating values will be discussed.
Product Backlog
Stories are waiting to be implemented in the backlog. Everything that should (or could) be done is stored here, but not in the next sprint. It makes sense to regularly Backlog Refinement to adjust or remove incomplete stories or stories that are no longer up-to-date.
