• Prescribed events are used by Scrum to create regularity and minimize the need for meetings not defined by Scrum. 
  • All events are time bound; in a "time-box", so that each event has a maximum duration. It helps everyone focus on the real problems, instead of going into too much unnecessary detail.

The nature of Scrum events : 



There are five events in a Scrum project: 

1. Sprint:

  • The heart of Scrum is a Sprint, which has a time-box of one month or less during which a functional and potentially publishable "Finished" Product Increment is created. 
  • Like a project, a Sprint is used to accomplish a goal. 
  • Sprints have a constant lifespan throughout the project. 
  • The Sprint is the container for the four other Scrum events, and a new Sprint begins immediately after the conclusion of the previous one.

2. Sprint Planning: it's the first event inside a Sprint. The Scrum Team plans the items they are going to deliver in the Sprint and the way they will deliver them. 

3. Daily Scrum: The Development Team starts working on the objectives of the Sprint as soon as Sprint Planning is completed. During the Sprint, the Development Team holds a daily meeting (normally 15 minutes) to coordinate the work for the next 24 hours. 

4. Sprint Review: before the end of the Sprint, the Development Team reviews the outcome of the Sprint with the customer to receive feedback. The feedback is used to adjust the Product Backlog. 

5. Sprint Retrospective: after the Sprint Review and just before the Sprint is over, the Scrum Team holds an internal meeting to review the Sprint (lessons learned) and use it to improve the process in the next Sprint. This meeting is called Sprint Retrospective. 

The four events inside the Sprint are designed to enable critical transparency, inspection, regularity, and adaptation.