Prescribed events are used in Scrum to create regularity and to minimize the need for meetings not defined in Scrum.
All events are time-boxed events, such that every event has a maximum duration. Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened. The remaining events may end whenever the purpose of the event is achieved, ensuring an appropriate amount of time is spent without allowing waste in the process.
Ceremonies | Definition / Purpose |
|---|---|
The Sprint | A sprint is a time boxed period during which specific work is completed and made ready for review. TNT Sprints are 2 weeks long. |
Sprint Planning | Sprint planning team meeting is a time boxed event that determine which product backlog items will be delivered and how the work will be achieved. The Scrum Team spend time planning the work of the sprint. The team works with the PO to understand in detail the items prioritized by PO at the top of the product backlog and the work required to complete them. Team commits to PBIs based on team capacity in a sprint. These items are moved to 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 daily scrum (stand-up) is a short communication meeting (no more than 15 minutes) in which each team member quickly and transparently covers progress since the last stand-up, planned work before the next meeting, and any impediments that may be blocking his or her progress. To synchronize the Teams efforts at meeting the Sprint Goal by sharing progress (done work), making commitments (planned work), and asking for help (blockers). Scrum Guide 2020 - No mention of 3 questions. Team to decide what works best for them.
|
The Sprint Review | The Sprint Review is the “show-and-tell” or demonstration event for the team to present the work completed during the sprint. 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 review is an opportunity for stakeholders outside the team to gain confidence in delivery by seeing working solution increments, and to provide feedback to ensure future work remains focused on delivering real business value. This is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit constructive feedback and foster collaboration. Why are sprint reviews important?
|
The Retrospective | The retrospective is the final team event in the Sprint to determine what went well, what didn’t go well, and how the team can improve in the next sprint. This is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning. The purpose of the Sprint Retrospective is to:
The retrospective meeting is for the team only. In order to create a safe space for team members to honestly reflect and collaborate on how the team could improve its delivery. |
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. Backlog Refinement provides an opportunity to bring clarity in expectations regarding behavior or functionality to be implemented through the Acceptance Criteria of that PBI. This is an ongoing process in which the team collaborate on the details of Product Backlog items. During refinement, items are reviewed and revised. Team is encouraged to size based on what they know at the time of reviewing PBI as it helps with the forecast. Why is refinement important?
|