Technical Leadership and Empowered Teams
summary
Argues that architects must stop dictating and instead act as roaming technical coaches who join teams and teach by doing, using mob programming to transfer skills quickly. Gives specifics: empowered teams deploy on demand and make large design changes; recommend two hours a day for about two weeks to learn mob technique; shows outcomes — faster onboarding, skill multiplication (one expert teaches many), and tools like a shared test automation framework that works better when built with team input rather than alone.
AI-written summary · about
chapters (18)
- 0:00Start
- 6:32The Science of Devops
- 7:44Empowered Teams
- 14:17How Skilled Is the Chef
- 15:17State of the Kitchen
- 18:12Mob Programming
- 19:51The Navigator
- 21:06The Working Agreement
- 24:05Measuring Productivity in Programmers
- 25:26Benefits of Mob Programming
- 30:35Teaching Tdd to a Team
- 31:12Collaborate with Other Coaches
- 35:34The Coding Dojo
- 37:06Summary Slide
- 39:38How Does Mob Programming Work with Remote Members
- 40:02How Do You Explain Value to Your Client
- 40:39How Do You Convince Your Business Stakeholders That It's Actually Worth It
- 41:05Is It a Good Idea To Empower a Team Which Does Not Have a Proper Skill Set
related talks
37mLearning technical practices using mob programming
02mHigh-performance teams
01h 04mAdvanced Software Teaming
03mCareer Advice for Architects
45mTeam and Software: Making an Impact as an Architect
01h 05mSoftware Teaming (Mob Programming) and the Power of Flow.
46mMob Programming, the True Approach to Team Development
40mThe Coaching Leader & Architect