‘Two People Struggling in Different Sites’ — How an Internal Community Linked Toyota-Style Agile Practice and What Came Next
summary
An internal chat led to building a company community that created an ongoing agile program and a TAC internal event (started March last year, opened to external participants in 2026). The talk describes Toyota-style agile practices applied to hardware Scrum across roughly eight teams: retrospectives, inception decks, trust-building facilitation to break vendor–Toyota silos, mob programming on an EV door team, and a vehicle-control TDD case; outcomes included restored team function, faster feedback, and many participants committing to adopt agile, while some practices (JDX, digital self-management) remain incomplete.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:13Toyota Agile origin
- 5:09Software team struggles
- 9:13Hardware team challenges
- 14:05Why Toyota needs Agile
- 16:00First Agile Challenge event
- 17:33Lessons from the event
- 18:49Future Agile plans
- 19:17Q&A: Resistance to Agile
- 21:05Q&A: Engineers' impact
- 22:27Closing
