Managing Quickscrum

QuickScrum Help

Scrum Ceremonies

Meetings or "ceremonies" are an important part of agile development. They help to empower the team and implement Scrum effectively. Every project has two elements - the content aspect (what you commit to achieving, such as writing software or implementing virtualization) and the process aspect (the activities you perform to keep the content work on track, such as updating Gantt charts and writing status reports). Scrum ceremonies refer to the "process" actions.


There are four main ceremonies or events in Scrum: 


       1.  Daily Scrum Meeting

       2.  Sprint Planning Meeting

       3.  Sprint Review Meeting

       4.  Sprint Retrospective Meeting


Scrum Ceremonies


1. Daily Scrum Meeting 


Each day at the same time, the team meets so as to bring everyone up to date on the information that is vital for coordination: each team members briefly describes any "completed" contributions and any obstacles that stand in their way. Usually, Scrum's Three Questions are used to structure discussion. The meeting is normally held in front of the task board. This meeting is normally time-boxed to a maximum duration of 15 minutes. To keep the meeting short, any topic that starts a discussion is cut short, added to a "parking lot" list, and discussed in greater depth after the meeting, between the people affected by the issue.


Also known as: 

  • The "daily stand-up"
  • The "daily scrum"
  • The "huddle"

 Read more about the Daily Scrum Meeting.


2. Sprint Planning Meeting


During Scrum Sprint Planning meeting event, the work to be performed in the Scrum Sprint is planned by the collaborative work of the entire Scrum Team. Items that will be delivered during the scrum sprint are acquired from the Product Backlog based on their business value. During scrum sprint planning, Scrum Team agrees on a scrum sprint goal that defines what the upcoming sprint is supposed to achieve. Later, the entire Scrum Team splits up work into individually developable units called tasks and team members accept the tasks based upon their levels of experience and expertise.


Read more about the Sprint Planning Meeting.


3. Sprint Review/Demonstration Meeting


Sprint review is a time to showcase the work of the team. The meeting can be casual or held in a more formal manner. The team demonstrates the work finished by them during the sprint and get feedback from the product owner and project stakeholders. The work should be fully demonstrable and meet the quality aspects to be considered as complete.


Read more about the Sprint Review/Demonstration Meeting.


4. Sprint Retrospective Meeting


After the sprint review meeting, the entire team gets together for the retrospective meeting. During this meeting, the team inspects and adapts its working process. During the meeting team members speak frankly about what occurred during the Sprint and how they felt about it. After all team members thoroughly understand each other, they work to identify what they’d like to do differently the next Sprint, typically focusing only on one or two specific areas of improvement each Sprint. The Scrum Master may also observe common impediments that impact the team and then work to resolve them.


Read more about the Sprint Retrospection Meeting.