Working with Others and Delivering as a Team — Bridges Seen Through Human Relationships
summary
Explains that many team failures are adaptive (people/relationship) problems rather than technical bugs and presents concrete fixes. Covers reviving a three-person QA/dev split over six months using daily huddles, negotiated norms (suggesting unit‑test tips not mandates), and role‑based task splits; resolving a product pivot from native iOS to LINE by clarifying decision timelines and running a focused offsite for alignment; and scaling an AI inventory-management project using Domain‑Driven Design, smaller user stories, and paired story‑writing to regain velocity.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 1:03Team conflicts
- 3:33QA bridging methods
- 6:25Policy shifts and dialogue
- 11:41Q&A
- 18:29Closing remarks
related talks
01h 00mImproving Your Team(work)
18mAgile leadership and technical mastery, a harmonious alliance
25mAgile: The Bad Parts - Matt Parker, Martina Hodges-Schell
32mPanel discussion: The journey to building effective engineering teams
46mEssentials for Building and Leading Highly Effective Development Teams
47mCodeCraft Leadership: Hacking the DNA of Agile Teams
38mHarmony in innovation - building stronger engineer-product relationships
41mKeeping distributed agile teams ‘face to face’