Scrum Ceremonies
As defined in the Scrum Guide, we adopt 4 key Scrum Ceremonies to be included into every sprint.
Sprint Planning
Sprint Planning initiates the Sprint by laying out the work to be performed for the Sprint. This resulting plan is created by the collaborative work of the entire Scrum Team. The attendees should be prepared to discuss the most important Product Backlog items and how they map to the Product Goal for the Sprint. The Scrum Team may also invite other people to attend Sprint Planning to provide advice. Sprint Planning is timeboxed to a 45 minutes per team meeting for a two-weeks Sprint.
Before the Sprint Planning the developers are kindly asked to pick the tasks for the upcoming Sprint from the Product Backlog and add them into the Sprint Backlog. Besides, to promote deeper tasks analysis and more precise planning, we kindly ask the participants to think of and list all possible risks and dependencies for the issue at question in the comments of the respective issue before the Sprint Planning. Besides, it is highly desirable that a short description of how a task is going to be executed be listed in the comments as well. The description should be short, precise and describe the logic of the solution that the developer anticipates.
Sprint Planning for Elastio teams is normally held on the first Monday of the Sprint. Additionally, teams are kindly asked to hold an Estimation Session in the beginning of the sprint to make sure all work planned is estimated.
Sprint Planning addresses the following topics:
- Why is this Sprint valuable?
The Product Owner proposes how the product could increase its value and utility in the current Sprint. The whole Scrum Team then collaborates to define a Sprint Goal that communicates why the Sprint is valuable to stakeholders. The Sprint Goal must be finalized prior to the end of Sprint Planning.
- What can be Done this Sprint?
Through discussion with the Product Owner, the Developers select items from the Product Backlog to include in the current Sprint. The Scrum Team may refine these items during this process, which increases understanding and confidence. Selecting how much can be completed within a Sprint may be challenging. However, the more the Developers know about their past performance, their upcoming capacity, and their Definition of Done, the more confident they will be in their Sprint forecasts.
- How will the chosen work get done?
For each selected Product Backlog item, the Developers plan the work necessary to create an Increment that meets the Definition of Done. This is often done by decomposing Product Backlog items into smaller work items of one day or less. How this is done is at the sole discretion of the Developers. No one else tells them how to turn Product Backlog items into Increments of value. The Sprint Goal, the Product Backlog items selected for the Sprint, plus the plan for delivering them are together referred to as the Sprint Backlog.
Daily Scrum
The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. The Daily Scrum is a 15-minute event for the Developers of the Scrum Team. To reduce complexity, it is held at the same time and place every working day of the Sprint. If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate as Developers. Daily Scrums help improve communications, identify impediments, promote quick decision-making, and consequently eliminate the need for other meetings.
Daily Scrum at Elastio is now done for each team separately, as is agreed within a team. Scrum of Scrums is held daily at 18.30.
Please note: Daily Scrum is currently replaced by Sprint Retrospective on the first Monday of a Sprint, and by Sprint Review on the last Friday of the Sprint.
Sprint Review
The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed. All tasks that can be presented as a Demo should be showcased as a part of Sprint Review, otherwise progress can be shown another way. During the event, the Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment. Based on this information, attendees collaborate on what to do next. The Product Backlog may also be adjusted to meet new opportunities. The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation.
Every participant should complete a list of tasks to be showcased at Sprint Review here.
The Sprint Review is the second to last event of the Sprint and is timeboxed to 2 hours for Elastio. It is normally held on the last Friday of the Sprint at 17.00.
Sprint Retrospective
The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. Inspected elements often vary with the domain of work. Assumptions that led them astray are identified and their origins explored. The Scrum Team discusses what went well during the Sprint, what problems it encountered, and how those problems were (or were not) solved.
As a result of the Sprint Retrospective the document should be completed for the previous Sprint.
The Sprint Retrospective concludes the Sprint. It is timeboxed to an hour and is held every first Monday of the following Sprint at 18.00.