Update your team to be more extreme
summary
Argues that changing team routines beats ad hoc fixes, offering five ideas (communication, feedback, simplicity, courage, respect) and concrete practices: adopt extreme programming habits like pair programming and test‑first, run code katas (Gilda Rose refactoring, bank kata, fizzbuzz) and short internal tech talks, and reserve regular slots — half an hour once or twice per month — for learning. Cites real artifacts: a webshop system, open‑source projects (FL, garcella Casella) as playgrounds to try these practices and measure improvement.
AI-written summary · about
chapters (10)
- 0:00Start
- 3:06How does a team work?
- 4:47What's the problem?
- 11:59Agile Manifesto
- 14:18Extreme Programming (XP)
- 16:42Some principles of XP
- 18:25What are the key challenges when adopting XP?
- 19:33How can you help your peers to embrace the change?
- 20:35What is a code kata?
- 24:01Recommended readings
related talks
49mExtreme Professionalism - Software Craftsmanship.
31mThe Effective Developer - Work Smarter, Not Harder
50mThe Effective Developer - Work Smarter, Not Harder
01h 03mThe Effective Developer - Work Smarter, Not Harder.
01h 06mTeaching New Tricks – How to enhance the skills of experienced developers
01h 01mKeynote: Software Craftsmanship – Growing a Technical Culture
17mGood to Great
33mHow to Enhance the Skills of Experienced Developers
