Scaled Retrospective – improvements bigger than a Scrum Team
summary
Scaled retrospectives run for groups of 50–70 people using a five stages flow: set the stage, gather data, generate insights, decide, close; teams submit top five priorities each, remote sites join by Skype and two days include face‑to‑face planning. First run yields ~70 topics and 29 action items of which 13 done (15 in progress, 1 blocked), so process shifts to quarterly cadence, top‑10 prioritization, posters/competition to boost attendance, agile radar and surveys to measure progress and improve cross‑location collaboration.
AI-written summary · about
chapters (21)
- 0:00Introduction to retrospectives
- 1:12Speaker introduction
- 1:56Company background and challenges
- 3:00Introducing tribes structure
- 5:57Shifting focus to workflow
- 7:01Redefining retrospective scope
- 8:09Five-step retrospective structure
- 10:40Assigning roles and responsibilities
- 12:47Gathering data from teams
- 14:13Creating action items and plans
- 16:18First retrospective mistakes
- 18:47Presenting the plan to the tribe
- 21:13Results and improvements over time
- 22:56Examples of changes introduced
- 24:47Key improvements made
- 27:22Making retrospectives engaging
- 28:48Refining the process
- 30:17Summary and call to action
- 31:24Q&A session introduction
- 32:13Retro of the retro
- 36:22Final Q&A and closing
related talks
08mHow to turn an agile retrospective into teambuilding
56mESSENTIALS - Retrospectives: Shifting Towards Value
32mRetrospectives
44mStop wasting your time with Retrospectives
45mAgile Retrospectives and the Agile Teams of Today and Tomorrow
01h 43mProject Retrospectives (Why, How, When)
20mOptimizing Agile Practices: The Retrospective
27m“Keep it simple!” Retrospecting on retrospectives