Seven Habits of a Highly Successful Team
summary
Practical habits from four years at iBOOD: teams split into microteams and use a cross‑functional tech board to enforce a strict 70/20/10 prioritization (70% innovation, 20% renovation, 10% lights‑on), break work into tiny experiments, and ship extremely small changes so pipelines push 40–50 releases per day. The team drops Scrum rituals, sprints, pull requests and heavy rules in favor of autonomy, pair/mob programming, weekly reprioritization and continuous delivery — a setup that survives outages but accepts fast failure as learning.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:49Technical debt in e-commerce
- 8:23Talk concept
- 10:09Purpose and priorities
- 15:45Killing complexity
- 21:22Autonomy in teams
- 27:15Communication practices
- 31:48Technical interruptions
- 34:49Continuous delivery
- 41:28Fun in teams
- 43:55Change and learning in tech
related talks
52mSmall Steps Are the Fastest Way Forward: Life Beyond Agile & Scrum
45mSoftware delivery with skills-based, self organising teams
36mDistributed & Local: Getting the Best of Both Worlds
14mGaining speed
27mTheory to action: Architecting and implementing your team operating system
39mProduct Teams: Complete Guide to Fantastic “Creatures”
33mReduce Small-Team Culture Shock with Agile
38mConway's law in practice: Agile teams & Microservises