The Sprint
The Sprint is the core of a Scrum project, representing a consistent duration of time during which a potentially shippable product increment is created. It provides a framework for regular feedback and inspected adaptation, which leads to a continuous improvement process. The duration of a Sprint is usually between 2-4 weeks and all work to be done is agreed upon during the Sprint Planning. During the Sprint, the Development Team works on completing the agreed tasks and the product increment is reviewed and assessed at the end of the Sprint during the Sprint Review. The Sprint concludes with a Sprint Retrospective, where improvements for the next Sprint are identified.
Guide: Understanding 'The Sprint' in Scrum Values
What is the Sprint?
The Sprint is the heartbeat of Scrum, where ideas are turned into value. It is a consistent, repeatable work cycle that happens in a specific timeframe (usually 1-4 weeks).
How it works?
At the beginning of a Sprint, the team holds a Sprint Planning meeting to agree on the set of product backlog items they will work on during the Sprint. The team then works on the items throughout the Sprint and present their work in a Sprint Review. After the Sprint, the team holds a Sprint Retrospective to reflect on their experience and to improve.
Exam Tips: Answering Questions on The Sprint.
Remember that the Sprint includes all the work and team collaboration from planning the work that will be done until the improvement of the process for the next cycle. A question could challenge you to identify the stages of a Sprint, sequence them accordingly or even criticize them effectively. Always remember that every Sprint's goal should result to value increments.
PSM I - The Sprint Example Questions
Test your knowledge of The Sprint
Question 1
In a Sprint Planning meeting, it's observed that the Product Owner is forcing the team to groom an item that will deviate the team from Sprint Goal. As a Scrum master, what would be your best course of action?
Question 2
In the middle of a Sprint, the team finds out that one of the Sprint tasks requires a specific set of skills that nobody in the team possesses. As a Scrum Master, what would be the best course of action?
Question 3
In the middle of a sprint, the team realizes the initial solution won't work and they need to re-design. What's the most proper course of action?