How to turn an agile retrospective into teambuilding
summary
A startup team of about 12–15 people split into four groups runs retrospectives without a dedicated Scrum Master and reports five concrete practices that work: no scrum master, replace childish games with a speed-dating format to pair-discuss sprint topics, rotate roles and perspectives so front end evaluates back end and vice versa, reserve 20 minutes for each subgroup, and publish action points on Slack with named owners and followup at the next retro.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 1:18Tip 1 Motivation
- 2:10Tip 2 Informal
- 3:36Tip 3 Rotation
- 4:40Tip 4 Discuss
- 5:28Tip 5 Summary
related talks
45mAgile Retrospectives and the Agile Teams of Today and Tomorrow
20mOptimizing Agile Practices: The Retrospective
39mScaled Retrospective – improvements bigger than a Scrum Team
01h 43mProject Retrospectives (Why, How, When)
48mStop Complaining& Start Learning! Retrospectives That Drive Change
42mA retrospective on retrospectives
56mESSENTIALS - Retrospectives: Shifting Towards Value
32mRetrospectives