Small Scale Scrumming
summary
Three cross-functional teams (three total) are coordinated by blocking a weekly mixed-session called trickster refinement where rotating reps refine, estimate and unblock work; a shared one backlog and open Slack channels with user groups plus JIRA labels and universal code review expose work and raise transparency. Calendar hours drop from 19 hours a sprint previously for both teams to about one hour less per developer on average, sprint goals become easier, ownership and motivation increase.
AI-written summary · about
chapters (11)
- 0:00Small Scale Scrumming intro
- 1:09Company background
- 2:55Merging conflicting teams
- 4:22Team coordination problems
- 5:45Shared identity and goals
- 7:08Restructuring mixed teams
- 8:57Communication and ownership
- 9:40Trickster Refinement meeting
- 12:27Results and benefits
- 13:32Key takeaways
- 14:16Q&A
related talks
15mAdvanced Scrum techniques for optimal delivery
05mScrumming Solo No Scrum Master or Product Owner
54mEffective SCRUM in Distributed Teams
35mScrum Overview
39mScrum at Scale
26mVirtual Scrum
19mTwo Examples of Scrum Master Initiatives Supporting the Whole Team in Large-Scale Scrum
16mScrum Buts - and how to remove them