Handling Complexity in Software Development Projects
summary
Project work splits into pre‑development (use Scrum, build demos), productization (apply V‑Model processes, docs, traceability) and fine‑tuning (app teams next to OEMs, travel for fast fixes). Architecture maps subcomponents on a Stacey matrix to pick team work modes; last year a new neural‑network architecture and radar vision parking replaced ultrasonic sensing using low‑level fusion. Integrate Scrum and waterfall with timeboxing and expect 80‑90% base reuse for parking; continuous DevOps and empowered local interfaces solve sync and deadline risks.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:03Why complexity matters
- 7:49Pre-development goals
- 12:52Transition to productization
- 15:24Productization trade-offs
- 24:17Final integration phase
- 29:12Key takeaways
- 30:38Q&A
related talks
39mSoftware development challenges in automotive projects
23mAchieving Both Quality and Development Speed in Toyota’s In-Vehicle Control Software — The Full Practice of Scrum × Test-Driven Development
49mIt’s Agile Jim, but not as we know it!
47mEmbedded Systems Architecture
20mDriving Intelligence: The Software Shift Shaping Tomorrow’s Cars
30mSoftware-Defined Vehicles and FOSS
11mBuilding the Software-Defined Vehicle
33mUnlock Embedded Excellence: Reliability Secrets Revealed!