Achieving Both Quality and Development Speed in Toyota’s In-Vehicle Control Software — The Full Practice of Scrum × Test-Driven Development
summary
The talk describes using Scrum combined with Test-Driven Development (TDD) for Toyota’s in-vehicle control software to reduce integration pain, maintain safety, and speed delivery. Teams run two-week sprints with rotating assistant scrum masters, pair and mob programming, and enforce a strict test pyramid (unit tests → parent-function tests → SIL → HILS) to catch faults earlier; distributed members use camera-on meetings and a fixed PO availability window. As a result, vehicle evaluation cycles that used to take about two weeks now finish in 2–3 days.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 3:07Scrum team structure
- 5:49In-vehicle software challenges
- 7:16Sprints and vehicle phases
- 8:41Supplier integration
- 10:04Vague specs handling
- 10:46TDD in practice
- 12:11Remote collaboration
- 13:02Team values
- 14:49Blame-free culture
- 16:15Adopting TDD
- 16:57Ambiguous tasks
- 18:00Scrum tracking
- 19:03Results and plans
- 21:27Q&A
related talks
40mAgile Software Development: Practice and Analytics
33mAgile Software Testing
44mHandling Complexity in Software Development Projects
39mScrum at Scale
01h 27mPNSQC 2014 - Halim Dunsky
43mBehavior Driven Development, or Agile 2.0
11mBuilding the Software-Defined Vehicle
24mTeams Developing Android/iOS Apps Together — Scrum Practices and Beyond