Effective SCRUM in Distributed Teams
summary
A case study of using Scrum across a 9-hour time-zone gap inside a 90,000-person biotech with a 1,500-person IT group. It describes concrete engineering practices—CI/CD, static analysis (Sonar/PMD), automated tests, code review or pair programming—and organizational measures—local product-owner proxy, weekly checkpoints, monthly code walkthroughs, domain-based module splitting—and shows how visiting labs, involving two PhD domain experts, and recording demos enabled timely scientist feedback.
AI-written summary · about
chapters (12)
- 0:00Start
- 6:14SCRUM framework
- 7:40SCRUM - agile principles
- 11:52BUSINESS KNOWLEDGE - solution
- 15:32ROLES - dev team
- 19:39ROLES - product owner
- 21:04ROLES - SCRUM master
- 22:57EVENTS - common rules
- 23:39EVENTS - Stand-up
- 25:24EVENTS - planning
- 26:43EVENTS - review
- 29:19EVENTS - retrospective
related talks
21mScaling Scrum in Fully Remote Work — Challenges from 3 People to 30 People and 6 Teams over Three Years and Applying Scrum@Scale and LeSS Practices
16mSmall Scale Scrumming
06mDistributed Teams
41mAgility in a Distributed Team
15mAdvanced Scrum techniques for optimal delivery
26mVirtual Scrum
19mTwo Examples of Scrum Master Initiatives Supporting the Whole Team in Large-Scale Scrum
39mScrum at Scale