Agile Stage-Gate: V-model + Agile for R&D projects

Hardware Agility does not replace the V-model, it complements it.
The exploration and technical validation phases benefit from short iterations to reduce risk. Industrialisation then follows a proven sequential process.

  • Iterative validations in the early stages
  • Controlled transition to industrialisation
  • Compatible with ISO 9001, ISO 13485, GMP, DO-178C

 Request a free presentation

How to combine Agile and the V-model

Example of hybrid management: Agile to V-model transition at TRL4
Example of a hybrid model with transition at TRL4 (the transition point varies depending on your context)

Early stages: Agile iterations

The exploration, feasibility and technical validation phases are characterised by uncertainty. Short iterations make it possible to:

  • Progressively validate technical choices
  • Integrate user feedback rapidly
  • Reduce risks before committing to industrialisation
  • Deliver functional proofs of concept at each cycle (2 to 4 weeks)

Industrialisation: the V-model

Once the product is stabilised, industrialisation demands rigour and traceability:

  • Frozen and validated specifications
  • Sequential process with formal milestones
  • Locked-down supply chain
  • Regulatory compliance assured

Our articles on Agility | Case studies

Agile Stage-Gate: the reference model for industrial R&D

Agile Stage-Gate combines milestone governance (go/no-go at each gate) with iterative execution between gates. This is the model we recommend for regulated R&D projects.

Unlike the classical Stage-Gate (sequential, rigid), Agile Stage-Gate introduces sprints between each gate. The team works in short iterations to explore and validate, then presents results to the steering committee at each gate. Go/no-go decisions are based on evidence of progress (validation reports, risk analyses, test results), not on forecast schedules.

Advantages of Agile Stage-Gate for industry:

  • Flexibility + control: teams iterate freely between gates, management retains milestone governance
  • Regulatory compatibility: gates correspond to certification milestones (ISO 9001, ISO 13485, DO-178C)
  • Risk reduction: each gate evaluates demonstrated maturity, not declared maturity
  • Pivot possible: if a gate reveals a major issue, the team can reorient before committing to industrialisation

Every sector, every organisation has its own constraints. We support you in building a bespoke hybrid management model.

Agile tools by regulated sector | Why not SAFe?

When to switch from Agile to the V-model

The transition between iterative and sequential approaches is not arbitrary. It relies on objective criteria that ensure the product is ready for industrialisation.

Transition checklist

  • Proof of concept validated: core functionalities confirmed by users
  • Specifications frozen: specifications document stabilised, accepted by stakeholders
  • Regulatory requirements validated: ISO, GMP, DO-178 compliance integrated
  • Supply chain locked down: qualified suppliers, components selected
  • Industrial process defined: production facilities, tooling, operating procedures ready
  • Risks under control: major uncertainties have been resolved

Common mistakes to avoid

  • Switching too early: committing to industrialisation whilst technical uncertainties remain leads to costly changes in later phases.
  • Switching too late: extending iterations beyond what is necessary slows time-to-market and increases development costs.
  • Lack of formal milestones: without objective criteria, the decision becomes subjective and a source of conflict.
  • Neglecting traceability: iterative working does not exempt teams from documenting technical choices for the industrial phase.

Compatible with your standards and frameworks

The hybrid model has been designed to integrate regulatory constraints from the outset, not as an afterthought. Normative requirements structure the early-stage iterations and guarantee a smooth transition to industrialisation.

ISO 9001

Decision traceability, document management, design reviews at each cycle. Iterative deliverables feed directly into the quality system.

ISO 13485

Medical devices: risk management (ISO 14971) integrated into cycles, DHF (Design History File) progressively populated.

GMP (Good Manufacturing Practice)

Pharma & biotech: formal equipment validations, IQ/OQ/PQ protocols prepared during the Agile phase, executed during the industrial phase.

DO-178C

Aerospace: certification objectives defined from the earliest cycles, automated requirements-to-tests traceability, audits at each milestone.

Key principle: Normative requirements are not a barrier to hardware agility, they define its guardrails. Each iteration respects the quality and regulatory criteria applicable to the current development phase.

FAQ: Agile vs V-model

What is the difference between the V-model and the Agile method in industry?

The V-model is a sequential process where each phase (specification, design, validation) follows the next with formal milestones. Agile is iterative: functional increments are delivered at each 2-4 week cycle. In industrial R&D, hybrid management combines both: Agile in uncertain upstream phases (exploration, feasibility, technical validation) then V-model for industrialisation where requirements are stabilised. The transition point depends on context: technological maturity (TRL), regulatory constraints, specification stability.

What is Agile Stage-Gate?

Agile Stage-Gate is a project management model that combines milestone governance (go/no-go at each gate) with iterative execution between gates. The team works in sprints between each milestone to explore and validate, then presents evidence of progress (validation reports, test results, risks mitigated) to the steering committee. Unlike the classical Stage-Gate (sequential, rigid), Agile Stage-Gate allows pivoting between gates if field data demands it. This is the model we recommend for regulated R&D projects (ISO 9001, ISO 13485, DO-178C).

How to combine Agile and the V-model in industrial R&D?

The combination of Agile and V-model follows one principle: use iterative methods where uncertainty is high, sequential methods where requirements are stabilised. In practice: upstream phases (TRL 1-4) run in Agile sprints with iterative POCs. When the proof of concept is validated and specifications are frozen, industrialisation switches to a classical V-model. Transition criteria are objective: proven technology, stabilised specifications document, locked-down supply chain.

Is Agility compatible with ISO 9001 and ISO 13485?

Yes. Neither ISO 9001 nor ISO 13485 requires a specific sequential process. They require traceability, document management and design reviews. Agile iterations feed the quality system at each cycle: industrial sprint reviews as validation milestones, documented deliverables at each iteration, decisions traced in the technical backlog. The hybrid model integrates these requirements from the start, not as an afterthought.

When to switch from Agile to the V-model in an R&D project?

The switch from Agile to V-model occurs when technical uncertainty is sufficiently reduced. Objective criteria: proof of concept validated by tests, specifications frozen and accepted, regulatory requirements integrated, supply chain locked down, major risks resolved. The classic mistake: switching too early (residual uncertainties that prove costly in the industrial phase) or too late (unnecessarily extended time-to-market).

How to manage an innovative project under high technical uncertainty?

A project under high uncertainty is steered through feasibility sprints (2-4 weeks) that each answer a specific technical question. Agile Stage-Gate structures governance: between each gate, the team iterates freely. At each gate, the committee evaluates demonstrated maturity (not declared) and decides: continue, pivot or stop. This approach embraces uncertainty instead of denying it through predictive planning.

Is Agile Stage-Gate compatible with DO-178C in aerospace?

Yes. DO-178C does not prescribe a specific development process, it defines certification objectives by criticality level. Agile Stage-Gate aligns naturally with these objectives: each gate corresponds to a certification milestone, requirements-to-tests traceability is built iteratively between gates, and audits rely on documented sprint reviews. The Scrum4DO178C approach (documented by IEEE) confirms this compatibility.

How to manage specification changes during an R&D project?

Specification changes are normal in R&D - they are a sign that the project is learning. Hybrid management absorbs them via a prioritised technical backlog: each change is evaluated (impact, cost, risk) and integrated into the next sprint if priority warrants it. The sprint review with the internal customer (or technical committee) validates choices at each cycle. The rule: accept changes in upstream phases (agile), freeze them during industrialisation (V-model). The Agile Stage-Gate materialises this transition point.

Ready to embrace Agility?

Training, coaching or a simple conversation - we are here to help