Sprint Flashcards
What is a Sprint?
Sprints are the heartbeat of Scrum, where ideas are turned into value.
A Sprint is a timebox of one month or less, during which a Done Increment is created that meets the Definition of Done and achieves the Sprint Goal.
What does Sprint contain?
Sprints contain the other Scrum events and the work to create the Increment. The Sprint is a container event for the other events and work.
What does a Sprint begin and end with? What happens during a Sprint?
A Sprint begins with Sprint Planning event and ends with the Sprint Review & Sprint Retrospective events.
The Daily Scrum event is held each day during the Sprint.
How long should a Sprint be? What is the consequence of a Sprint that’s too long or too short?
A Sprint should be short enough to allow the Scrum Team to maintain focus but long enough to deliver an Increment that meets the Definition of Done.
If a Sprint is too long the definition of what is being built may change, complexity may rise, and risk may increase.
If Sprints are too short it may not be possible to produce an Increment that meets the Definition of Done.
When can shorter Sprints be used?
Shorter Sprints can be employed to generate more learning cycles and limit the risk of cost and effort to a smaller time frame. Each Sprint may be considered a short project
When can the length of a Sprint change?
The length of a Sprint can change if the Scrum Team decide to do so and there is a good reason for it. This should be an infrequent occurrence and Sprint duration should not be changed whilst a Sprint is underway.
What are the benefits of having Sprints with consistent durations?
Sprints have consistent durations. Consistent Sprint durations reduce complexity and increase predictability. A new Sprint starts immediately after the conclusion of the previous Sprint. There are no gaps between Sprints.
Do Sprints include non-working time?
Sprints include non-working time such as weekends and holidays. This means that the amount of working time may vary.
What are the rules during the Sprint?
During the Sprint:
- No changes are made that would endanger the Sprint Goal;
- Quality does not decrease;
- The Product Backlog is refined as needed; and,
- Scope may be clarified and renegotiated with the Product Owner as more is learned.
