Scrum Events are mandatory opportunities given by Scrum to Inspect and Adapt. The reason they are mandatory is that Scrum is a inspect-adapt way of solving complex adaptive problems. If we do not use the minimum opportunities then a fundamental aspect of Scrum is compromised. These events are specifically designed to enable critical transparency and inspection. Failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt.
Scrum Events create regularity and 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.
There are 5 Events in Scrum
- Sprint – which is container of all the other events
- Sprint Planning
- Daily Scrum
- Sprint Review
- Sprint Retrospective
Following is the summarization of all events
| . | SPRINT | SPRINT PLANNING | DAILY SCRUM | SPRINT REVIEW | SPRINT RETROSPECTIVE |
|---|---|---|---|---|---|
| TIMEBOX | 1 Month or Less | 8 Hours max for one month sprint. For shorter sprint, this event is usually shorter | 15 minutes maximum regardless of the length of the sprint | 4 Hours max for one month sprint. For shorter sprints, this event is usually shorter | 3 Hours max for one month sprint. For shorter sprints, this event is usually shorter |
| WHO ATTENDS | This is a container event and Scrum team performs the work during the Sprint | Scrum Team | Developers | Scrum Team and Stakeholders | Scrum Team |
| OPTIONAL ATTENDANCE | Any one involved with the product may help the Scrum team to improve the product and the effectiveness | Anyone invited by Scrum Team. Usually SMEs from business or technical side. | Ideally no one But Developers may Invite. | Anyone invited by scrum Team | STRICTLY no one else other than the Scrum Team |
| PURPOSE | Build an increment, keep evolving the Sprint Backlog as more is known, refine the product backlog by taking feedback continuously from Product Owner and Stakeholders | Initiate the Sprint by laying out the work to be performed for the Sprint. This involves preparing a Sprint Goal, forecasting items to be done this sprint and a plan to go with it. | Inspect progress towards the Sprint goal, plan next 24 to 48 hours which involves adapting the Sprint Backlog if necessary | Inspect the increment and adapt the product backlog | 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. |
| INPUT | - | Product backlog, Increment, Velocity (Past Performance), Capacity Available, Improvements identified in the retrospective, Definition of Done | Sprint Goal, Sprint Backlog, Work done over the last 24 hours | Product Increment, Progress towards the Product Goal, Market place conditions | Individuals, interaction, process, tools, definition of done |
| OUTPUT | Product Increment | Sprint Backlog | Updated Sprint Backlog | Updated Product Backlog | Improvements identified, Adapted DOD |
| Role of Developers in this event | Build the increment | Create Sprint Forecast and Plan | Update Sprint Backlog | Help the PO take feedback from the stakeholders. Collaborate with stakeholders to better understand the future requirements. | Collaborate to identify Improvements |
| Role of Product Owner in this event | Manage Product Backlog, ensuring requirements are understood by Developers, providing feedback on a day to day basis, clarifying if required | Collaborate with the Developer | None. May be invited by Developers to attend to clarify doubts. | Collaborate with Stakeholders, update the product backlog for next sprints, understand market place conditions and take decisions on what needs to be done, making release plans | Collaborate to identify Improvements |
| Role of Scrum Master in this event | Scrum is enacted properly. Guide, Mentor, Coach Scrum Team. Facilitate Scrum Events. | Facilitation which involves ensuring the meeting happens, Timbox is respected, Every one understands the purpose, Meeting is positive | Facilitation if required which involves observing and seeing if Developers are adjusting their Sprint Backlog and planning the next 24-48 hours. | Facilitation which involves meeting happens, Timebox is respected, Every one understands the purpose, Meeting is positive and productive | Facilitate the event, Coach the Scrum Team by sharing observations, Collaborate to identify Improvements, Ensuring that this meeting does not become a blame-assignment forum |