Events involved in a Sprint

Scrum 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.

Scrum Events

Other than the Sprint itself, which is a container for all other events, each event in Scrum is a formal opportunity to inspect and adapt something. 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.


The Sprint

It is the basis of the Scrum. It is a period of 1 month, 3 or 2 weeks, during which an increase of product, usable and potentially releasable, is created. Ideally, they always have the same duration.

A new Sprint begins immediately after the conclusion of the previous Sprint.

A sprint is made up of Sprint Planning, Daily Scrums, development work, Sprint Review, and Sprint Retrospective. (Read More...)

Sprint Planning

The work that will be carried out in the Sprint is planned in Sprint Planning, through the collaboration of the entire Scrum team.

The duration of the Sprint planning should last a maximum of 8 hours for a one-month Sprint, and if the Sprint is shorter, the event is usually shorter. (Read More...)

Daily Scrum

The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. This is done by inspecting the work since the last Daily Scrum and forecasting the work that could be done before the next one.

The Daily Scrum is held at the same time and place each day to reduce complexity. 

For more information on daily scrum, please click here...

Sprint Review

A Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint. Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on the next things that could be done to optimize value.

This is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration.

For more information on Sprint Review, please click here...

Sprint Retrospective

The Sprint Retrospective 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.

• - This is a three-hour time-boxed meeting for one-month Sprints.

• - For shorter Sprints, the event is usually shorter.

• - The Scrum Master ensures that the event takes place and that attendants understand its purpose.

• - The Scrum Master teaches all to keep it within the time-box.

• - The Scrum Master participates as a peer team member in the meeting from the accountability over the Scrum process. 

For more information on Sprint Review, please Click here...