Uncover key trends in Scrum meetings. Explore the most frequent Scrum ceremonies among companies and what these patterns reveal about their Scrum practice maturity. Get insights on Agile adoption through meeting analysis.
Companies starting with agile meetings are gradually maturing by holding more Daily Standups, indicating a growing agility posture.
Retrospectives empower teams to pinpoint their strengths and areas for growth, facilitating alignment and collective focus on improvement.
Teams perform retrospectives at least once a month, to check on how they work together and grow as a team.
New action items
Around 3 action items are added per retrospective. Teams actively seek areas for further improvement.
resolved action items
Taking action to improve at the same pace with action items items!
Teams keep retrospective meetings long enough.
A big part of the retrospective is spent on members collecting their notes.
Almost 3 days. Remote participants have 3 full working days to contribute in the team retrospective!
A full day and a halfis spent on gathering thoughts. Remote teams take their time during async retrospectives to properly share their notes.
Beyond gathering notes,
the discussion stage is where teams spend their time.
Participants discuss to create meaningful action items.
Daily Standups foster team alignment on current projects, facilitate the resolution of blockers, and ensure focus on priority tasks.
Every 2nd working day teams align their focus.
7 to 8 people teams working on scrum/agile.
Teams slightly prefer meeting in person for their daily standups, rather than not meeting or conducting them asynchronously.
2.25 hours per month is spent on an in-person standup meeting. Validating and unblocking work increments.
Average speaking time
Usually one or two members dominates a synchronous standup with updates.
Covering all timezones, as the maximum possible time difference is 12 hours.
in chat app
1 in 2 teams use an established chat service for their daily standup.
Planning poker helps the team refine upcoming work and provide an unbiased estimate of the effort required. During this ceremony, the team usually refines blurry aspects of future work.
Members votes are not that aligned over the effort needed for upcoming work.
Average voted effort
Between 5 and 8 of Fibonacci scale for story point estimation. Tasks that are voted tend to be large, some further breakdown could be useful.
Teams spend a significant time on each task during a session. This means that voted tasks are well defined.
Read on how to perform retrospective, daily scrum, and backlog refinement rituals with remote teams.
Take action to improve your team's daily happinessTry out Team O'clock for free