Translations:Sprint/2/en
Characteristics
When starting to work with Scrum, it is advisable to consider the sprint as the event that contains all the others:
- It sets the pace of daily progress and makes it possible to visualize and share it in the Daily Scrum.
- It sets a fixed rhythm for checking product development in Sprint Planning and Sprint Review.
- Retrospectives are held at that same rhythm, to reflect and improve. In more mature adoptions of Scrum, however, the scope of the sprint can be considered to be only the building of the increment, leaving the meetings aside. This may be of interest to the team, for example, to calculate sprint velocity considering only working time, excluding the opening, closing, and retrospective meetings; to have greater flexibility when running sprints of different lengths; or to decouple the frequency of retrospectives from that of sprints.
Principle and values
- Continuous improvement: the pace of progress in iterations makes it possible to detect problems early and to continuously improve both the product and the process. At the end of each sprint, the team has tangible evidence of what has worked and what needs to change.
- Timeboxing: the fixed length of the sprint acts as an engine of progress, counters Parkinson's Law, and creates the urgency needed to prioritize and make decisions.
- Transparency and inspection: the sprint produces visible results at regular intervals, which allows stakeholders to inspect the product's actual progress—not documents or estimates—and adapt the direction if necessary.