There are 4 ceremonies in Scrum process.

1. Sprint Planning Meeting
2. Daily Scrum
3. Sprint Review Meeting
4. Sprint Retrospective Meeting

Other than that, there is a Product Backlog Refinement meeting.

The backlog grooming meeting is attended by the team, the Product Owner, and the Scrum Master. During the meeting, everyone works together to PREPARE the backlog for the next sprint planning meeting. This might include adding new stories and epics, extracting stories from existing epics, and estimating effort for existing stories

1. Increases EFFICIENCY of the team by greatly reducing uncertainty and unknowns.
2. Better refined stories are more accurately estimated, more accurately tested, and more accurately implemented
3. Increases efficiency of the team due to the benefit of shared knowledge gained by the entire Scrum team being in the refining.
4. Allows the team to maintain a sustainable, higher pace.
5. When done well, refining greatly reduces the time required for a Sprint Planning meeting.

• Sprint Planning Meeting: 
  • Attendees: Development team, Scrum Master, Product Owner
  • When: At the beginning of the sprint.
  • Duration: Approx 120 min for a 2-week iteration
  • Purpose: Product owner comes with the prioritized backlog and then the Scrum Team plans the items they are going to deliver in the Sprint and the way they will deliver them, estimate them, and break them into tasks.
• Daily Scrum: 
  • Attendees: Development team, Scrum Master, Product Owner
  • When: Once per day preferably in the morning.
  • Duration: 15 min 
  • Purpose: 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. This meeting is called the Daily Scrum. 

Have each team member answer the following questions:

• What did I COMPLETE yesterday?
• What will I work on today?
• Am I blocked by anything?
• Do not discuss any technical details and issues in detail. You can do that right after Daily Scrum with the chosen members only.
• Sprint Review:
  • Attendees: Development team, Scrum Master, Product Owner
  • Optional-Project Stakeholders
  • When: At the end of the sprint.
  • Duration: 30 -60 minutes
  • Purpose: Before the end of the Sprint, the Development Team presents (demonstrates) the outcome of the Sprint to the customer and receives feedback. This meeting is called the Sprint Review (also known as Sprint Demo). Remember, work should be fully demonstrable and meet the team's quality bar to be considered complete and ready to showcase in the review.
• Sprint Retrospective 
  • Attendees: Development team, Scrum Master, Product Owner(optional)
  • When: At the end of an iteration
  • Duration: 30 -60 minutes
  • Purpose: After the Sprint Review, the Development Team holds an INTERNAL meeting to review the Sprint and use it to improve the process (lessons learned) in the next Sprint. 

Also, find out what's not working and use the time to find creative solutions and develop an action plan. Scrum Master facilitates this meeting. We generally use sticky notes in which each team member writes three things about sprint (which just got over.)

1. What shall we continue?
2. What needs to be stopped?
3. What needs to be started?

Then the Scrum Master discusses the issues (without specifying anyone’s name) and develops the action plan.

Continuous improvement is what sustains and drives development WITHIN an agile team, and retrospectives are a key part of that.