Your team spends 1.5 months of a person’s bandwidth a year on retrospectives — so make ‘em count
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 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 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 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 retrospectives? We’re here. Our plug and play retrospectives tool syncs between Slack and Jira to give you a seamless, 360 solution with automated reminders, recaps, exporting, and syncing.
There are easier ways to improve team health with retrospectives. We’d love to show you. Visit sprintlio.com to learn more.