Agile leadership and technical mastery, a harmonious alliance
summary
Team moves a UX designer into the squad, gets one backend liaison and coaches an architect to share knowledge, resulting in partial success; dual‑track discovery cuts dead features using a usage index and deliberate deletions; CI/CD push raises automated test coverage to 80% but is blocked by authority; GitHub Copilot adoption claims a 26% productivity boost after security negotiation; pair/mob programming and peer review reduce rework; technical debt is rated per module and 10% sprint capacity is dedicated to refactoring, removing red modules in a year.
AI-written summary · about
chapters (10)
- 0:00Agile leadership basics
- 1:07Excessive dependencies
- 3:14Developers excluded
- 5:27Painful releases and CI/CD
- 6:32AI developer support
- 8:18Poor source control use
- 10:49Avoiding pair/mob programming
- 11:13Ignoring technical debt
- 13:19Leaders fostering excellence
- 14:02Q&A
related talks
51mSabotaging a Transformation
47mCodeCraft Leadership: Hacking the DNA of Agile Teams
52mToo many cooks! Supporting augmented teams without getting salty
24mOvercoming Resistance: UX Practices in Agile Teams
22mOptimizing Product Development: Balancing Speed, Quality, and Process
35mBuilding and Growing an Agile Team
01h 10mAgile Cross Team Collaboration How Tos
25mAgile: The Bad Parts - Matt Parker, Martina Hodges-Schell