It’s Agile Jim, but not as we know it!
summary
Dyson is already running over a million connected products and is trying to ship devices that combine embedded to cloud to mobile integration plus robotics and ML without reverting to waterfall. Engineering institutes a ten-week planning cadence with low‑resolution planning to force cross‑discipline alignment, seconded infrastructure/security/test experts into teams, and aims for continuous delivery. A pragmatic, selective SAFe adoption surface‑tests coordination: regular ten‑week integrations improve visibility and release predictability, but architectures, global team design and unplanned ops still demand manual tradeoffs.
AI-written summary · about
chapters (19)
- 0:00Intro
- 2:34Lean software In a waterfall world
- 3:48Business Interactions
- 4:48Interfacing with Milestones
- 7:57Combining disciplines
- 8:43Incremental delivery
- 10:07How & when to align?
- 12:16Growing pains
- 13:17Principles
- 14:04Team design
- 16:42Team Responsibilities
- 21:32Logical Levels of Change
- 25:39Aligning more than software
- 26:35Work was not visible
- 27:13Global Optimizations dyson Without breaking too much
- 29:34The simplest thing?
- 31:23Common framework
- 36:37Common Approach
- 44:25Regular integration cadence
related talks
44mHandling Complexity in Software Development Projects
26mDevOps Insights for the Executable Digital Twin
23mAchieving Both Quality and Development Speed in Toyota’s In-Vehicle Control Software — The Full Practice of Scrum × Test-Driven Development
01h 05mAgile embedded development under regulatory constraints
05mDevOps on 36 Ton Machines: Shipping Software to Autonomous Excavators in the Desert
33mUnlock Embedded Excellence: Reliability Secrets Revealed!
11mBuilding the Software-Defined Vehicle
49mImplementing Modern CI in an IoT Medical Device