Sprint Retrospective Time Min

Sprint retrospective: time-boxing the inspection

The Sprint Retrospective closes out the sprint. It's where the Scrum Team looks back at how the last iteration went across people, interactions, processes and tools, then settles on what to improve. The Scrum Guide 2020 caps it at three hours for a one-month sprint, which puts the standard time-box for a two-week sprint at 1.5 hours. This estimator scales that proportionally, total_min = semanas × 45, and nudges the figure up by team size once conversation overhead starts to matter.

Common formats include Start-Stop-Continue, 4Ls (Liked, Learned, Lacked, Longed for), Sailboat (anchors, winds, rocks, island) and Mad-Sad-Glad. Catalogs like Retromat and the Liberating Structures repertoire give you ways to mix up the dynamic so the team doesn't slide into one repetitive ritual. Behind it all sits the Japanese idea of kaizen, or continuous improvement.

Applications

Scrum Masters reach for this calculator when blocking the right calendar slot to invite the team. Agile coaches use it while planning a Retrospective of Retrospectives (RoR) in scaled frameworks such as SAFe and LeSS. And engineering managers use it to budget non-delivery time during capacity planning.

FAQ

Can the retrospective be shorter than 1.5h? Yes. The Scrum Guide caps the duration but never sets a minimum. Small teams of 3–4 people often wrap up in 45–60 minutes. Go much lower than that and you start risking the action-item step getting skipped.

How many action items should we leave with? One to three concrete improvements works best. Pile on more and the team usually fails to land any of them in the next sprint.

Should we invite the Product Owner? Yes. The Scrum Guide 2020 treats the PO as part of the Scrum Team, so participation is expected unless the team explicitly agrees on a different setup.