# Agile V-Model, anybody?

In the era of software-defined vehicles, OEMs are aiming to decouple mechanical, electrical/electronic (E/E), and digital (software and AI) workstreams to enable **multi-speed development**. As shown in the diagram, this decoupling ensures that each stream operates at its own optimal pace. The **digital workstreams** must support rapid iteration cycles, often measured in hours or days, enabling frequent updates, feature improvements, and testing. In contrast, **E/E workstreams** require a medium-term focus, typically spanning weeks, to ensure robust system integration and validation. Finally, the **mechanical workstreams** follow a long-term development cadence measured in months, driven by extensive physical testing, safety requirements, and production timelines.

<figure><img src="https://392531723-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRqBHYU6DD895ydQm5PcS%2Fuploads%2FiUbc1Abg5Wwmg0iFvE4I%2Fimage.png?alt=media&#x26;token=65e8e9c4-5918-43c3-9afc-df791b0d9e0d" alt=""><figcaption></figcaption></figure>

To achieve this multi-speed approach, OEMs must establish **clearly defined technical and organizational interfaces**. On the technical side, key enablers include **loose coupling** between the layers of development, supported by **hardware abstraction layers (HAL)** and **vehicle hardware abstraction layers (VHAL)**. This abstraction allows software and digital innovation to advance independently of hardware constraints. The concept of **"Shift North"** further supports this, enabling non-safety-critical software functions to reside in higher-level compute environments where rapid changes can occur without impacting lower-level systems.

Organizationally, this decoupling requires well-defined workflows, tools, and responsibilities across teams. By creating interfaces that align development priorities and testing processes, OEMs ensure seamless collaboration while maintaining the integrity of long-term physical systems and fast-moving digital innovation.

Additionally, this approach aligns with the **Shift Left** strategy, which emphasizes early-stage digital validation through simulation, virtualization, and continuous testing. This minimizes costly late-stage errors and ensures that the digital, E/E, and mechanical streams can efficiently converge during system integration, verification, and production.

Ultimately, this multi-speed, decoupled development approach provides OEMs with the agility to innovate quickly in the digital space while maintaining the reliability and safety of the physical vehicle systems.