Retrospective Timer OnlineFree retrospective timer for agile sprint retrospectives. Time each retro phase (gather, generate, decide, close) to keep team reflection efficient.Frequently asked questionsHow long should a sprint retrospective be?Scrum Guide recommends a maximum of 3 hours for a 4-week sprint, 90 minutes for a 2-week sprint, and 45–60 minutes for a 1-week sprint. In practice, 60 minutes is typical for 2-week sprints. A timed retrospective produces crisper insights than open-ended sessions.What are the phases of a retrospective and how do I time each?Classic 4-L's retro (60 min): Check-in 5 min, Liked (10 min), Learned (10 min), Lacked (10 min), Longed For (10 min), Action planning (15 min). Set the timer for each phase independently. The time pressure prevents the group from dwelling on any single item.How do I keep the retrospective on time when the team has a lot to say?Use dot voting (each person gets 5 votes, marks their top concerns) during the "generate" phase to surface the top 3 items before discussion starts. This prevents the loudest voice from dominating and ensures the timer is spent on the most valued topics.What's the best retrospective format for a remote team with the timer?Use Miro or Mural (virtual sticky note boards) with timed phases. "Quiet writing time" (5 minutes, timer visible) prevents anchoring — everyone writes before sharing. Then rotate through sticky notes. The timer ensures equal attention to all contributions before discussion.How many action items should come out of a retrospective?1–3 action items maximum, each with a named owner and a deadline. More than 3 rarely get implemented. Use the last 15 minutes of the retrospective timer to agree on actions — not to generate more discussion. Quality of follow-through matters more than quantity of ideas.