How microteams change the way we collaborate. Again.
summary
Argues teams shrink to one–three people who form, finish an item, then disband, organized as collectives (skill pools) inside areas (value streams); uses Cynefin and the Golden Circle to justify moving from projects to continuous flow, heavy automation (CI/CD pipelines, unit/acceptance tests) and fewer rules. Gives concrete evidence: a repository of ~3,000 LOC with 342 unit tests, Amazon-style deployment rates of ~7,000+ releases/day as an existence proof, and Quby running 1 TB/day of household data to predict boiler failures, showing microteams accelerate delivery and reduce dependencies.
AI-written summary · about
chapters (7)
- 0:00Introduction and speaker intro
- 8:18Why projects don't work anymore
- 15:41Shorter cycles and continuous delivery
- 22:19Moving beyond traditional agile
- 30:02Complexity of modern software development
- 36:15Working in microteams
- 46:10Call to action and conclusion
related talks
47mHow Microteams Change the Way We Collaborate. Again
01h 00mHow microteams change the way we collaborate
21mAutonomous Teams
47mMicroservices and the Inverse Conway Manoeuvre
51mTech-enabled Network of Teams
01h 05mSoftware Teaming (Mob Programming) and the Power of Flow.
01h 01mRip It Up And Start Again?
58mMicroservices and the Inverse Conway Manoeuvre