A group of seven sits and stands at a conference table while another person addresses the group. Scrum ceremonies can help teams improve their processes, increase efficiency and create innovative solutions during product development. These meetings allow team members to collaborate throughout the Scrum process so they can work together toward shared goals. Understanding the various types of Scrum ceremonies can help you implement and execute them successfully within your team.

1. Benefits of Scrum
Ceremonies
Jyoti Bhatt

2. Lack of etiquette and manners is a huge turn off.
KnolX Etiquettes
 Punctuality
Join the session 5 minutes prior to the session start time. We start on
time and conclude on time!
 Feedback
Make sure to submit a constructive feedback for all sessions as it is very
helpful for the presenter.
 Silent Mode
Keep your mobile devices in silent mode, feel free to move out of session
in case you need to attend an urgent call.
 Avoid Disturbance
Avoid unwanted chit chat during the session.

3. 1. What is Scrum
 Brief introduction of scrum
 Pillar of scrum
 Artifact in scrum
 Values of scrum
2. Ceremonies in scrum
 Scrum Ceremonies
 Benefits of scrum ceremonies

5. Brief Introduction of Scrum
Why is it called Scrum?
People often ask, “Is Scrum an acronym for something?” and the answer is no. It is actually inspired by
a scrum in the sport of rugby. In rugby, the team comes together in what they call a scrum to work
together to move the ball forward. In this context, Scrum is where the team comes together to move the
product forward.

6. Brief Introduction of Scrum
 According to The Scrum Guide, scrum is "a lightweight framework that helps people, teams and organizations generate
value through adaptive solutions for complex problems. "Scrum is the most widely used and popular agile framework”.
 Scrum is an empirical process, where decisions are based on observation, experience and experimentation.
 Think of empiricism as working through small experiments, learning from that work and adapting both what you are
doing and how you are doing it as needed.
 Scrum is light-weighted framework that emphasizes self-organization. It is simple to understand and help the team to
work together

7. Pillar of Scrum
There are three pillar of scrum:-
 Transparency
 Inspection
 Adaption

8. Pillars of Scrum

9. Artifacts of scrum
Artifacts in Scrum are information that describe the
product, the work, and the progress of the project.
There are three artifacts of scrum:-
 Product Backlog
 Sprint Backlog
 Increment

10. Product Backlog Sprint Backlog
List of all the items that need
to be completed for
developing the end product.
List of items to be completed
in each sprint
Product owner collects the
backlog from the customer
and assigns to the team
The team collects the
backlog from the PO and
decides the time frame to
complete during each sprint
Specific to the end goal Specific to the sprint
The entire set of work in
progress.
The subset of the product
backlog
Independent of the sprint
backlog
Purely dependent on the
product backlog
Product owner owns it Scrum team owns
Until the completion of the
entire project, the PO will
maintain the backlogs
Every new sprint will get new
backlogs added by the team

11. Product Increment
 A product increment is the customer deliverables that were produced by completing product
backlog tasks during a sprint.
 It also includes the increments of all previous sprints.
 There is always one increment for each sprint and an increment is decided during the scrum
planning phase. An increment happens whether the team decides to release to the
customer.
 Product increments are incredibly useful and complementary to CI/CD in version tracking
and, if needed, version rollback.

12. Scrum Values

13. Scrum Ceremonies
Scrum ceremonies are time-boxed meetings or events that ensure the three primary roles, including the scrum master,
product owner, and development team, are in sync. These scrum ceremonies, or events, are conducted at particular
instances during the Agile sprint cycle, which we will outline below:-
 Sprint planning
 Daily – Stand up meeting
 Sprint review
 Sprint retrospective and
 Backlog refinement meeting
The terms scrum events, Agile ceremonies, scrum ceremonies, scrum meetings, and Agile meetings are frequently used
interchangeably or in place of each other. Although the agendas for these scrum events are similar or related, it's
important to note the key differences between the Agile framework and scrum teams.

15. The Sprint Planning

16. Benefit of Sprint planning
 Increased Focus
When your team members have a crystal-clear idea of what their 2-week sprint looks like, there's no room for
other projects to get in the way. Each team member has something they need to focus on for those two weeks,
and when the whole team finishes each part, major initiatives get completed faster.
 Increased Transparency
Sprint planning meetings generally include the entire Scrum or Agile team. Including everyone in
the meeting ensures that no one has any questions about what other people are working on. As a result, it’s
less likely that the team duplicates work as everyone plans a sprint together.
 Teams produce higher quality work
By incorporating user stories and allowing team members to focus on specific tasks, sprint planning helps
team members produce higher quality work

17. Daily- Stand Up

18. Benefits of daily-stand
 Reduce Roadblocks
Bringing any hangups to the team’s attention sooner rather than later means you can develop a solution more
quickly. Waiting days or weeks to do this wastes valuable time, so checking in daily means you’ll be more
productive overall.
 Improve collaboration
A daily stand-up is a great way to assess how members of your team could be working together on present or future
projects.
 Encourage positive team building
The more co-workers are around each other, the more comfortable they’ll be with speaking up and offering
feedback.

19. Sprint review
 Sprint review conduct at the day of
sprint closure.
 Present what team accomplished.
 Demo new feature developed.

20. Benefit of sprint review
 Feedback and Validation
Stakeholders can witness a physical presentation of the product increment at the Sprint Review Meeting, which gives
them a chance to provide instant feedback and validation on the features that have been delivered.
 Maximizing Value Delivery
The team makes sure that the end users are receiving the most value possible from each iteration by focusing on
examining the increment’s alignment with the sprint objective and stakeholder expectations.
 Improved Communication
By promoting open discussion among the development team and stakeholders, the sprint review helps everyone
understand the project’s objectives, status and obstacles.

21. Sprint Retrospective
Whole team discuss the result of last sprint

22. Benefit of Sprint Retrospective
 Celebrate things that are going well
Positive feedback not only provides clarity on what the team should keep doing—it also keeps your team engaged,
promotes teamwork and reduces the negative effects of stress.
 Identify areas for improvement
Identifying ways to optimize your sprint process is essential—because without constructive feedback, you and your
team can’t improve.

23. Product Backlog Refinement meeting

24. Benefit of product backlog refinement meeting
 It increases the efficiency of the team by reducing uncertainty.
 Properly refined stories are easy to estimate, test, and implement.
 PBR session increases the efficiency of the team due to the knowledge shared among the team members.
 If the PBR meeting is maintained properly, it helps reduce the time for a Sprint planning meeting.

25. Benefits of Scrum Ceremonies

27. Increased innovation
Having a clear time frame and frequent meetings for a project can help all team members stay focused and execute their tasks
promptly. It also allows teams to discuss challenges and develop solutions with other team members. This approach can help
ensure all team members meet the requirements and priorities of a sprint.
Improved customer satisfaction
Scrum ceremonies generate customer satisfaction by allowing members of the development team to consider new ways to add
value to a product. Using the product backlog, the Scrum team can understand their goals. They can also identify how they can
improve and create solutions throughout product development.

28. Clear expectations
Scrum ceremonies allow for cross-functional collaboration and establish expectations for members of the Scrum team. This
approach can ensure all team members understand their roles and responsibilities and may lead to the faster production of
deliverables, as everyone clearly understands their objectives. Team members also know who to approach for guidance
regarding particular tasks.
Collaboration across channels
When Scrum teams hold ceremonies, they foster effective communication among stakeholders, the product owner and the
development team. A cross-functional approach usually helps teams generate innovative business solutions. In this way,
ceremonies can help ensure the delivery of high-quality products and the continual production of new concepts and ideas.