Empowering Teams To Change
summary
7digital reorganizes from component teams into cross‑functional feature teams (teams of about 4–6 people) that pull work from a single backlog shown on a physical campaign board and tracked in Jira; the change is done iteratively from the ground up, with weekly staggered support rotations and strict SLE gating. The claim is concrete: within months many engineers can pick up any codebase, defects drop because fresh eyes fix issues immediately, throughput and value delivery increase, and gaps in specialist skills are addressed via proposed community of practice groups.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:52Key factors for success
- 3:14Iterative reviews and team sharing
- 4:39Future improvements with communities
- 6:05Commercial context understanding
- 6:48Cross-functional teams expansion
- 8:34Q&A on campaign board
- 10:05Avoiding specialization
- 11:10Balancing support and development
- 12:36Managing support workload
- 14:02Support team rotation
- 15:11Concluding stand-up
related talks
58mDevs fight your Battle! A Pledge for cross-functional Teams
20mBuilding High-Productivity Teams Focused on Outcomes: Team Design and Collaboration Case Studies
44mScaling Agile With a Super-Effective Global Delivery Machine
14mGaining speed
35mTeam transformation to accelerate value delivery
47mHow Microteams Change the Way We Collaborate. Again
46mScaling Agile in your Organization with the Spotify Model
20m"Self-Designing Teams" Workshop