TK Ceremonies / Events
- Samir Sheikh (Unlicensed)
The Sprint is a container for all other events. Each event in Scrum is a formal opportunity to inspect and adapt Scrum artifacts. These events are specifically designed to enable the transparency required. Failure to operate any events as prescribed results in lost opportunities to inspect and adapt. Events are used in Scrum to create regularity and to minimize the need for meetings not defined in Scrum.
Optimally, all events are held at the same time and place to reduce complexity. (Scrum Guide)
Ceremonies | Definition / Purpose |
|---|---|
The Sprint | A sprint is a time boxed period during which specific work is completed and made ready for review. |
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 Scrum Team spend time planning the work of the sprint. The team works with the PO to understand PBIs to be worked in a sprint from the product backlog and the work required to complete them. Team commits to PBIs based on team capacity in a sprint, which are moved to the Sprint backlog. To ensure the team remains focused and the work of the sprint is coherent, the team works with the product owner to articulate a sprint goal, a simple statement of the objective of the sprint or the purpose of the next solution increment. |
The Daily Scrum (Stand-up) | 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 members of the Scrum Team. If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate as Developers. Team can select whatever structure and techniques they want, as long as their Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable plan. This creates focus and improves self-management. |
The 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. The Product Owner (PO) checks the work against pre-defined acceptance criteria and either accepts or rejects their work. The stakeholders or clients give feedback to ensure that the delivered increment met the business need. The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation. |
The 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. The Scrum Team discusses what went well during the Sprint, what problems it encountered, and how those problems were (or were not) solved. The Scrum Team identifies the most helpful changes to improve its effectiveness. The most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint. |
Backlog Refinement | Not an official event / ceremony of a scrum. It is encouraged for the team to meet regularly and refine backlog items to get ready for upcoming sprints. The Scrum Team decides how and when refinement is done. Product Backlog refinement is the act of breaking down and further defining Product Backlog items into smaller more precise items. This is an ongoing activity to add details, such as a description, order, and size. Attributes often vary with the domain of work. Members who will be doing the work are responsible for the sizing. The Product Owner may influence the Developers by helping them understand and select trade-offs. |