A Good Team is Not a Dream
summary
Concrete claims and practices: teams scale to 150 QA people and hiring one person costs five to six interviews = 12–30 hours, so replace “we can survive without them” thinking. Problems get fixed in solve in 30 minutes not 3 weeks timeframes; leaders act as supporters, run retrospectives, set clear expectations (deadlines, check-ins midweek), give constructive feedback immediately, provide training links, empower decision-making by voting, and mentor with real tasks and measurable goals.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:11Team communication mistakes
- 5:43Authority vs leadership
- 10:19Problematic leadership
- 13:13Team roles
- 16:01Mentoring skills
- 21:23Lead by example
- 24:54Successful mentee
- 25:59Mentoring program rules
- 31:44Burnout recognition
related talks
16mTear Down the QA Wall
20mWorking with Others and Delivering as a Team — Bridges Seen Through Human Relationships
52mDeveloper Joy – How great teams get s%*t done
33mBuilding Sustainable Teams to Handle Uncertainty
16mIs Our Team as Resilient as Our Systems?
27mLeading a Team with Values
34mDebug Your Team and Maximize Its Potential
30mHerding Tigers - Software Development and the Art of War