My Tiny Phoenix Project
summary
A team intervention replaces a single hero with shared ownership by enforcing three concrete rules: never come in empty handed, escalate gradually and everyone does code reviews. The team tracks who knows which systems, runs monthly retrospectives and pairs reviews (peer then senior), and measures waiting time and review load. After three months reviewers improve, after six months juniors lead projects and the former bottleneck takes two full offline vacations with no incidents. The bus factor rises and on-call fatigue drops.
AI-written summary · about
chapters (5)
- 0:00Start
- 11:25Escalate gradually
- 12:24PRINCIPLES
- 19:03All team members do code reviews, gain confidence
- 22:47NOT DONE YET
related talks
34mBecoming a team, one pixel at a time
01h 01mPairing, Sharing, Caring - One team's journey to Pair Programming
25mRethinking measurement for high-performing teams
56mHow to really work as a team- from sleepy to strong pair programming
01h 00mMob Programming, A Whole Team Approach
41mTurn Up the Good
54mMob Mentality Collaborative Coding and Problem Solving
44mInspect & Adapt, then What?