Scrum Ceremonies Radar

Find out which Scrum events are working for your team.

Try this health check live

What is the Scrum Ceremonies Radar?

Scrum events drift. Stand-ups start running long, and retros turn into routine. The Scrum Ceremonies Radar asks your team to rate five parts of its Scrum practice: Backlog Grooming, Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective. Each event has one statement, such as "Our stand-ups are short, to the point, and helpful," rated from 1 (Strongly Disagree) to 5 (Strongly Agree). Because everyone rates on their own, the radar shows where the team agrees an event is working and where people see it differently. Pick the lowest-scoring event, agree on one change to try next sprint, and run the radar again to see whether it helped.

Dimensions

Scrum Ceremonies

Evaluate how effectively each core Scrum event supports your team's flow, alignment, and ability to deliver.

  • Backlog Grooming

    Our approach and tools keep the backlog up to date and prioritized for future sprints.

    • Strongly Disagree
    • Neutral
    • Strongly Agree

  • Sprint Planning

    Our planning sets our team up for success throughout our sprints.

    • Strongly Disagree
    • Neutral
    • Strongly Agree

  • Daily Scrum

    Our stand-ups are short, to the point, and helpful.

    • Strongly Disagree
    • Neutral
    • Strongly Agree

  • Sprint Review

    Our showcases reflect the sprint goals and the team's effort and velocity.

    • Strongly Disagree
    • Neutral
    • Strongly Agree

  • Sprint Retrospective

    Our retros are meaningful and enable us to continuously improve and overcome obstacles.

    • Strongly Disagree
    • Neutral
    • Strongly Agree

When to use this health check

  • When your Scrum events feel like routine, run long or no longer earn their time
  • At a quarterly or release review of how your sprint cadence is working
  • When a new Scrum Master or coach wants a baseline on how each event is going
  • After a change in team members, sprint length or working agreements
  • As a recurring check, to see how each event's score moves over time

Tips & tricks

  • Have everyone rate on their own before discussing, so quieter people's views show up
  • Focus on the lowest-scoring event and agree on one experiment to run next sprint
  • Run the radar again every few sprints to see whether the changes are sticking
  • Back each low score with an example from a recent sprint, so the feedback is something the team can act on
  • Ask the Product Owner to rate too, especially on backlog grooming and sprint review

Frequently asked questions

What does the Scrum Ceremonies Radar measure?
How well each of five Scrum practices works for your team: backlog grooming, sprint planning, daily scrum, sprint review and sprint retrospective. Each one gets a statement to rate, so you can see which needs attention.
Who should take part?
The whole Scrum team, including developers, the Scrum Master and the Product Owner. Each role experiences the events differently, so you need all of them.
How often should we run it?
Every few sprints or once a quarter. That's often enough to see trends without people tiring of the questions.
How is it scored?
Each event is rated from 1 (Strongly Disagree) to 5 (Strongly Agree). The results show as a radar of where your events are strong and where they need work.

Related health checks