Scrum is a framework for developing and sustaining complex products. The Scrum Guide contains the official definition of Scrum as authored by Ken Schwaber. Scrum is an agile framework for managing work with an emphasis on software development. It is designed for development teams from three to nine members. Scrum is defined in the Scrum Guide by Ken Schwaber and Jeff Sutherland, the originators of Scrum and is translated and available in over 30 languages.
|Author:||Tanya King DDS|
|Published:||11 October 2014|
|PDF File Size:||40.77 Mb|
|ePub File Size:||21.29 Mb|
|Uploader:||Tanya King DDS|
Scrum (software development) - Wikipedia
The Scrum process A sprint or iteration is the basic unit of development in Scrum. The scrum guide deutsch is a timeboxed effort; that is, it is restricted to a specific duration.
Each sprint ends with a sprint review and sprint retrospective,  that reviews progress to show to stakeholders and identify lessons and improvements for the next sprints. Scrum scrum guide deutsch working product at the end of the sprint that scrum guide deutsch really done. In the case of software, this likely includes that the software has been fully integrated, tested and documented, and is potentially shippable.
- Nexus Guide German Audio |
- Scrum Guide Downloads | Scrum Guides
- Homepage |
- 2018 Nexus Guide German Audio
- Scrum (software development)
- Global Scrum Community
Daily Scrum[ edit ] A daily scrum in the computing room. This centralized location helps the team start on time.
Each day during a sprint, the team holds a daily scrum or stand-up with specific guidelines: All members of the development team come prepared.
During the daily scrum, each team member typically answers three questions: What did I complete yesterday that contributed to the team meeting our sprint goal? What do I plan to complete today to contribute to the team scrum guide deutsch our sprint goal?
The Scrum Guide
Do I see any impediment that could prevent me or the team from meeting scrum guide deutsch sprint goal? No detailed discussions should happen during the daily scrum.
Sprint review[ edit ] At the end of a sprint, the team holds two events: At the sprint review, the team: Reviews the work that was completed and the planned work that was not completed Presents the completed work to the stakeholders a.
Incomplete work cannot be demonstrated The recommended duration is two hours for a two-week scrum guide deutsch proportional for other sprint durations At the sprint retrospective, the team: Reflects on the past sprint Identifies and agrees on continuous process improvement actions Guidelines for sprint retrospectives: Two main questions are asked scrum guide deutsch the sprint retrospective: What went well during the sprint?
What could be improved in the next sprint?
Scrum guide deutsch recommended duration is one-and-a-half hours for a two-week sprint proportional for other sprint durations This event is facilitated by the scrum master Extensions[ edit ] The following activities are commonly done, although not considered by all as a core part of Scrum: Backlog refinement[ edit ] Backlog refinement once called backlog grooming is the ongoing process of reviewing product backlog items and checking that they are appropriately prioritised and prepared in a way that makes them clear and executable scrum guide deutsch teams once they enter sprints via the sprint planning activity.
Product backlog items may be broken into multiple smaller ones; acceptance criteria may be clarified; and dependencies, investigation, and preparatory work may be identified and agreed as technical spikes.
This is a concept in software development that reflects the implied cost of additional rework caused by choosing an easy solution now instead of using a better approach that scrum guide deutsch take longer.
Cancelling a sprint[ edit ] The product owner can cancel a sprint if necessary.