Return to site

SCRUM THEORY: The Scrum events 🥳

· team,scrum

All the events of Scrum have a maximum duration, i.e. the event is over if the time-box expires. 

The events can also be over before the expiry of the time-box if the objectives of the event have been achieved, but it cannot extend beyond the timebox.


💡 A Sprint is a container for all the other events.

The other events that are contained in a Sprint are as follows:

👉 Sprint Planning

👉 Daily Scrum

👉 Sprint Review

👉 Sprint Retrospective


The four prescribed events each serve a purpose and provide an opportunity for Inspection and Adaptation.

Excluding any event would mean forgoing the purpose of that event as well as losing an opportunity to inspect and adapt which is at the heart of every successful implementation.

The time-box of each of the events are as follows:

👉 Sprint Planning – 8 hours or lesser

👉 Daily Scrum – 15 minutes

👉 Sprint Review – 4 hours or lesser

👉 Sprint Retrospective – 3 hours or lesser


💡 Daily Scrum is a daily event for the development team aimed at synchronizing them to what has been achieved, and to plan the work for the next 24 hours.

Any impediments are also brought up in this event. It is one of the more important events which helps the development team in tracking their progress.

Only the development team members participate in the daily scrum. Other stakeholders like the Scrum Master, Product owner, etc., can attend the Daily scrum, but are not allowed to participate.


💡 Sprint Review is a four hour or shorter meeting held at the end of the Sprint to inspect the Increment created during the Sprint and adapt based on observations of the stakeholders.

The primary activities of Sprint Review are:

👉 Demonstration of the “Done” work items

👉 Collaboration on what needs to be done next

The result of the Sprint Review is a revised Product Backlog that defines the probable Product Backlog items for the next Sprint.

The Product Backlog may also be adjusted overall to meet new opportunities.


💡 Sprint Retrospective is typically the last event of the Sprint, and one of the key inspect events in Scrum, and usually an outcome of this event is a lessons learnt/action plan for improvement.

The purpose of Sprint Retrospective is:

👉 Inspect how the last Sprint went with regards to people, relationships, process, and tools;

👉 Identify and order the major items that went well and potential improvements; and,

👉 Create a plan for implementing improvement