Doing Scrum with Multiple Teams
summary
The talk explains how the FreeIPA (IdM) project adopted Scrum across multiple teams, covering why they chose Scrum, how they configured the project in Jira, and how they appointed a dedicated Scrum Master. It describes their reorganization from one large distributed team into smaller, technology-focused stable teams and how the Product Owner role emerged from existing team members, and it summarizes lessons learned and future plans.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:55Multiple teams
- 7:54Core Scrum principles
- 13:19Daily Scrum challenges
- 19:53Timeboxing and planning
- 25:14Team communication
- 31:23Lessons learned
- 37:16Workflow adjustments
- 42:31Interdependent tasks
- 46:24Measuring productivity
- 48:11Q&A
related talks
54mEffective SCRUM in Distributed Teams
35mAgile Scrum Overview
19mTwo Examples of Scrum Master Initiatives Supporting the Whole Team in Large-Scale Scrum
05mScrumming Solo No Scrum Master or Product Owner
16mSmall Scale Scrumming
39mAgile Scrum Overview
54mScrum Masters Are Not Alone! Communities as Spaces for Recovery and Growth
56mImpediments: Effective Management When Scaling Scrum