Make your Sprint Retrospective actionable
Too much discussion and not enough action?
Run your Sprint Retrospective on Teamworki, set action items and hold your team accountable with automated reminders.
Configurable boards
Create a Retro board based on a template (e.g. Mad/Sad/Glad) or bring your own.
Easy access via Slack, Microsoft Teams, and email
Whenever you start a retrospective, the entire team gets a notification with an access link. No more emails back and forth.
Facilitate the discussion
During the discussion stage, the facilitator can highlight a card – which will make it pop up on everybody’s screen – while your team is logging the discussion as comments.
A timer is available to avoid side discussions.
Hold each other accountable
Create action items and define due dates. Before starting your next sprint retrospective, easily visualize which items from the previous session are still standing.
NEW: create action items as JIRA issues and track them using Teamworki. Learn more.
Gauge the sentiment of your Retros
After the Retrospective, get AI-powered insights on the sentiment of the team’s feedback.
Teamworki has made it very simple for us to proactively spin up a new virtual Retrospective at the beginning of the sprint, enabling users to add feedback throughout the sprint.
Drew Podwal
Head of Business Agility
MadHive
WHAT IS THE PURPOSE OF A SPRINT RETROSPECTIVE?
Sprint retrospectives bring the team together to celebrate what went well, identify opportunities for improvement, and set clear action items as a way to address that feedback.
Often taking place at the end of the work sprint (1-4 weeks), they have a structure: members add items to a board, they vote for the ones they agree the most with, and then the top items are discussed, sparking action items.
Learn here some tips for running an effective sprint retrospective in agile teams.
