Here's how much time your team spends on agile retrospectives
August 15, 2019
An engineering team of 10 people who work 40 hours a week for 50 weeks a year and run on biweekly sprints spends about 260 hours a year in agile retrospectives. That’s 6.5 weeks of a single person’s time. If your team’s average salary is $100K, that’s $13,000 just on agile retrospectives.
Depending on the pizza size and the team’s preference for Agile ceremonies, these figures can change but the message is the same: If your team is running agile retrospectives, make them count.
- Do they fail to accomplish anything? That’s an easy fix.
- Is the participation really week? Here’s why.
- Are the meetings getting dominated by an individual? Solve it.
- Is your team not picking up the habit? Maybe give it a bit more time.
- Is the discussion really surface-level? Remove the recency bias.
Need help making the most of your team’s agile retrospectives? We’re here. Our plug and play agile retrospectives tool syncs between Slack and Jira to give you a seamless, 360 solution with automated reminders, recaps, exporting, and syncing.
How to close your agile retrospective meeting
The work isn’t done for the facilitator when the agile retrospective meeting ends. There are some key steps you’ll want to take to make sure the meeting is as effective as possible and we’re here to give you all the secrets for post-meeting success.
What is the most popular agile retrospective meeting format?
We've all been there. Tasked with facilitating the next scrum retrospective and cruising Retromat for a fresh meeting format recommendation to spice things up…
The numbers are clear — here’s what your agile retrospectives are missing
When we built Sprintlio as an agile retrospectives tool, it was our belief that if your team didn’t take the time between sprints, releases, iterations, or…