Scrum events are time boxed meetings set up to create regularity and to minimize the need for meetings not defined in Scrum. Each event in a sprint, with sprint itself being a Scrum event, is a formal opportunity to inspect and adapt something. These events are 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.

There are mainly five events as per SCRUM:
1. Sprint
2. Sprint planning
3. Daily scrum
4. Sprint review
5. Sprint retrospective

Let’s now deep dive into each one of these events

Sprint

Input: A Sprint goal, Sprint backlog and plan of execution
Output: Usable and Potentially releasable done increment
Time box: One month or less
Participants: SCRUM team

A sprint is the heart of Scrum. A sprint consists of Sprint planning, Daily scrums, the actual development work, Sprint review and the Sprint retrospective.
The empirical values of Inspection and Adaptation are showcased in this event as timely (once every sprint) inspection of the done increment helps the scrum team and the stakeholders to adapt with the market changes and make necessary changes to make sure that the product which goes out to the market is of utmost value

Sprint Planning

Input: Product backlog, the latest product increment, projected capacity and past performance of the Development Team
Output: A Sprint goal, Sprint backlog and plan of execution
Time box: 8 hours for a one-month sprint
Participants: SCRUM team

Sprint planning helps the development team to plan for the work to be performed in the sprint. The Scrum team discusses and plans for what can be delivered as an increment resulting from the sprint and how to achieve this. The number of items selected from the Product Backlog for the Sprint is solely up to the Development Team. Only the Development Team can assess what it can accomplish over the upcoming Sprint.
The empirical value of Transparency is showcased in this event as the development team is open enough to accept what can be achieved and what cannot. Also, the values of Inspection and Adaptation come to the fore as the Scrum team does not blindly commit on any sprint goal or backlog. It inspects the previous increment delivered and considering the sprint goal and projected capacity of the team, pulls in enough work into the sprint, not more not less.

Daily Scrum

Input: The progress towards the sprint goal made in the past 24 hours and the impediments faced, if any
Output: The plan for the next 24 hours to progress towards the sprint goal and any open impediments
Time box: 15 minutes
Participants: Development team

The Daily Scrum is held every day of the Sprint. During this event, the Development Team plans on what is to be achieved in the next 24 hours. This event optimizes team collaboration and performance by inspecting the work since the last Daily Scrum and forecasting upcoming Sprint work. The Daily Scrum is held at the same time and place each day to reduce complexity.

The daily scrum can be conducted in different ways as per the development team’s feasibility as long as it focusses on the progress towards the sprint goal. One of the widely used structure is as shown below:
• What did I do yesterday that helped the Development Team meet the Sprint Goal?
• What will I do today to help the Development Team meet the Sprint Goal?
• Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?

All three empirical values are showcased in this event. The development team is transparent about what has been and what could not be achieved. They inspect what was the reason why a task/work item could not be achieved and how best can they adapt to get it done at the earliest and progress towards the sprint goal.

Sprint Review

Input: Work done as part of the current sprint, the done increment and discuss on changes to the marketplace or potential use of the product
Output: An idea on what is the most valuable thing to do next which will help the team formulate a revised Product Backlog that defines the probable Product Backlog items for the next Sprint
Time box: 4 hours for a one-month sprint
Participants: Scrum team and stakeholders invited by the Product Owner

All three empirical values are showcased in this event as the SCRUM team is transparent about what has been achieved and what could not be achieved. The participants in this event, inspect the increment, its value out in the market, what changes might bolster the market value of the product and adapt the product backlog if needed with the changes discussed.

Sprint Retrospective

Input: How the last sprint went with regards to people, relationships, processes and tools
Output: Improvements to be enacted during the next Sprint and a plan for implementing them
Time box: 3 hours for a one-month sprint
Participants: Scrum team

All three empirical values are showcased in this event. The scrum team is transparent about what went well during the sprint, what they feel didn’t go as good as expected and needs to be improved. Also, the participants in this event, inspect the learnings from the sprint with regards to people, relationships, processes and tools and formulate action points to adapt the learnings in the upcoming sprint(s).

Foot note
A good read – The 5 Most Common Pitfalls of the Scrum Events by Barry Overeem
https://www.scrum.org/resources/blog/5-most-common-pitfalls-scrum-events

LEAVE A REPLY

Please enter your comment!
Please enter your name here

*