Here you will find the definitions of the most important terms from this chapter.
A Sprint is a time-boxed iteration in which the Scrum Events (Sprint Planning, Daily Scrums, Sprint Review and Sprint Retrospective) are processed and the Product Owner's ideas are converted into valuable results (= Increments). A Sprint lasts a month or less, a new Sprint starts directly after the previous Sprint has been completed.
Sprinting is the time when the Increment is actively worked on and developed, therefore Sprinting plays a central role during the Sprint. It always takes place between the Sprint Planning Meeting and the Sprint Review. Each day during the Sprinting, the Daily Scrum Meeting is held.
In an iterative procedure, or when work is done in iterations, the goal is approached step by step - in the case of Scrum, the Developers approach the Sprint Goal gradually.
Please answer the following questions independently. Take your time and think carefully about what you want to answer before having a look at the solutions.
What events take place between two Sprints?
There is no event between two Sprints because one Sprint seamlessly leads into the next Sprint.
What is the objective of each Sprint?
The objective of each Sprint is to create a potentially deliverable Increment, not the entire product. This means that the Developers create a thin vertical slice of the whole product per Sprint.
Which characteristic is required of an Increment at the end of a Sprint?
The Increment at the end of a Sprint should be potentially deliverable - this does not mean that it has to be delivered. It should be publishable or deliverable to the customer after each Sprint, but it is by no means an obligation to actually deliver the Increment.
Who determines the Sprint duration and what is the maximum duration of a Sprint?
The duration of the Sprint is determined by the Product Owner, taking into account a number of factors. A Sprint may not last longer than 4 weeks.
What is the optimal Sprint duration?
It is not possible to make a general statement about the optimal duration of a Sprint, as this depends on a number of factors. If the project is complex, a Sprint should tend to be shorter. In addition, the Sprint should only last as long as the business risk is manageable. It is also a good idea for the Sprint to last long enough so that other business matters can be synchronised with the Sprint.
Why are sprints time-boxed?
The reason for Sprints being time-boxed is simple: if the process from idea to finished product is condensed and correspondingly short, problems can be identified and process weaknesses can be detected at an early stage.
Which are the official Scrum Events?
- Sprint Planning Meeting
- Daily Scrum
- Sprint Review
- Sprint Retrospective