Is industrial Agility comparable to software developer Agility?

No. Industrial Agility requires deep adaptations to handle physical deliverables, multi-site and cross-functional teams, as well as integrated risk management, unlike purely software artefacts.

Why not apply IT Agile methods directly to industry?

The contexts are radically different. Industry has strong trade-specific constraints (physical deliverables, manufacturing lead times, regulatory standards) that require a specifically adapted hybrid version.

How do you convince leadership that industrial Agility is not an IT fad?

By presenting concrete results such as Airbus (-10% costs), by highlighting the industrial origin of the approach that accounts for physical constraints, and by showing documented sector references.

Do you still follow the Agile Manifesto?

The Agile Manifesto was written in 2001 for software developers. It is now considered outdated in demanding professional environments. SolidCreativity critiques it for its counter-productive effects on modern Agility.

Can you mix Agile with ISO 9001/13485 standards?

Yes, through adapted document management and the articulation between iterative cycles and quality audits. Integration with GMP and ISO 13485 is possible, as demonstrated by our references in the pharmaceutical sector.

What types of projects are suited to industrial Agility?

Non-predictive early stages, complex and innovative multi-site projects, and all cases where the V-model shows its limits in terms of flexibility and responsiveness.

Is Agility compatible with heavily regulated projects?

Yes, for example in pharma with GMP requirements. Iterative cycles can be adapted to audits while maintaining ISO 13485 compliance.

How do you adapt Agility to industrial subcontracting constraints?

Through contractualised supplier cycles, ultra-short technical check-ins (15-30 minutes) and a collaborative evaluation grid to maintain alignment.

How do you introduce Agility in a company?

Start with a pilot project accompanied by training, then progressively adapt the tools. Measure with concrete indicators such as lead times and review pass rates.

What budget should you plan for a first Agile experience in industrial R&D?

Budget EUR 5 to 10k for a pilot team. Return on investment typically comes within 3 to 6 months, measurable through reduced delays and improved review pass rates.

Do you need to hire a Scrum Master for industrial projects?

No, it is sufficient to train an existing project manager. The training takes just a few days and this approach has proven successful with clients such as ArcelorMittal.

What tools should you use for visual management in an industrial environment?

Excel spreadsheets combined with physical Post-it notes, a burn-down chart, and collaborative tools suited to multi-site teams.

Our senior engineers are sceptical. How do you convince them?

Through hands-on experimentation on a sub-project. A 2024 study shows that 90% of sceptics change their mind after trying the method, and often become active advocates.

Hybrid Management: Agile + V-Model for innovative industrial projects

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

Adapt this model to your context

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

Request a free assessment Let's discuss your challenges Discover our training courses 5 courses from field teams to leadership

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.

Ready to embrace Agility?

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

Training 5 courses from field teams to leadership Coaching Tailored support Contact Let's talk about your needs

Hybrid Management: Agile in early stages, V-model for industrialisation