Scrum learning - Time Box Events
15 minute is not enough to bring your work on new level? This isn’t so when it comes to Scrum. Fourth part of our course – Time Box Events.
The Sprint
The heart of Scrum is a Sprint, a time-box of maximum one month during which releasable product increments are created. Sprints contain and consist of the Sprint Planning, Daily Scrums, the Sprint Review, and the Sprint Retrospective.
Sprint Planning
The work to be performed in the Sprint is planned at the Sprint Planning. This plan is created by the Scrum Team. Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint.
The Scrum Master ensures that the event takes place and that attendants understand its purpose. The Scrum Master teaches the Scrum Team to keep it within the time-box. Sprint Planning answers what is result for the upcoming Sprint, how the result will be achieved?
Daily Scrum
The Daily Scrum is a 15-minute event for the Development Team. It’s held every day, at the same time and place each day.
Such meeting is only for Development Team members, as the plan of work belongs entirely to them. The Daily Scrum is the best opportunity to re-plan the Sprint Backlog as a result of new experience learned during the last working day.
Each team member should be able to tell about:
- What he or she did yesterday
- What he or she intend to do today
- Any impediments which are getting in their way
By the end of the Daily Scrum, the team have a clear plan for the next 24 hours. The Daily Scrums improve communication, highlight and promote quick decision-making, and improve the Development Team’s level of knowledge.
Sprint Review
A Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. This is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration.
- This is at most a four-hour meeting for one-month Sprints.
- The Product Owner explains what Product Backlog items have been “Done” and what has not been “Done”;
- The Development Team demonstrates the work that it has “Done” and answers questions about the Increment;
- Review of how the marketplace or potential use of the product might have changed what is the most valuable thing to do next;
- Review of the timeline, budget, potential capabilities, and marketplace for the next anticipated releases of functionality or capability of the product.
Sprint Retrospective
The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.
It’s a maximum three-hour meeting. The Scrum master ensures that the meeting is positive and productive. The purpose of the Sprint Retrospective is to:
- Inspect how the last Sprint went with regards to people, relationships, process, and tools.
- Identify and order the major items that went well and potential improvements.
- Create a plan for implementing improvements to the way the Scrum Team does its work.
During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by improving work processes or adapting the definition of “Done”, if appropriate and not in conflict with product or organizational standards.
So, our series come to the end. Next Friday - Scrum and NITG.