Medical Device Development Insights: Agile Product Development Within a Regulated Medical Device Environment

This article is part of ATL’s Medical Device Development Insights series, which explores the engineering processes used to bring safe, effective medical devices from concept to market.

Overview

In medical device development, speed and compliance are often viewed as opposing forces.

Agile development is associated with rapid iteration, fast feedback, and frequent learning. Regulatory frameworks such as FDA design controls, EU MDR, and ISO 13485 are more commonly associated with structured documentation, traceability, formal reviews, and waterfall-style development.

At first glance, those two approaches can seem difficult to reconcile.

At ATL, we see them differently.

Agile methods can be used to de-risk and accelerate product development, provided they operate within a controlled and compliant development framework.

The key is not replacing regulatory structure with Agile methods. It is using Agile thinking inside that structure to create faster learning, earlier feedback, and better-informed design decisions.

Regulation Requires Control, Not Rigidity

Regulatory standards do not prevent iteration.

What they require is control.

FDA design controls, EU MDR, and ISO 13485 expect documented design inputs and outputs, formal design reviews, traceability, and verification and validation activities.

These requirements naturally align with a waterfall structure at the program level. There are defined phases, required deliverables, and formal checkpoints that must be maintained.

But within those phases, iteration can still happen.

Agile methods can be used effectively when the iteration is:

• planned
• documented
• reviewed
• traceable

This is where the distinction matters.

Agile development in a regulated environment is not informal development. It is disciplined iteration within a controlled framework.

Agile Within the Waterfall Model

At ATL, Agile practices are embedded within each waterfall phase rather than used to replace the waterfall model entirely.

The waterfall structure provides the compliance framework. Agile practices provide the learning loops inside that framework.

Those loops may include:

• rapid prototyping
• design reviews
• tooling iterations
• process development feedback
• early functional testing
• manufacturing feasibility checks

The value is not simply moving faster.

The value is learning earlier.

When teams can evaluate assumptions quickly, they can identify technical, manufacturing, and usability risks before they become larger project issues.

What Makes Agile Possible in Regulated Development

Agility is not created by a single process, software tool, or project management method.

It depends on capability.

To iterate quickly in medical device development, teams need access to the right expertise at the right time.

That includes:

• design engineering
• process development
• tooling
• manufacturing
• quality
• test capability

When those disciplines operate separately, even small changes can create significant delays.

When they are integrated, decisions can be made quickly and with the right technical context.

This is one of the key advantages of ATL’s product development center of excellence in Cardiff, where in-house capability allows design, tooling, manufacturing, and quality teams to work together closely throughout development.

A Practical Example: Agile Iteration in Action

A practical example is a customer issuing a design update late in development.

In a traditional outsourced model, even a minor change can create significant timeline impact. The update may need to move between design teams, external tooling suppliers, manufacturing partners, and quality reviewers before a representative part can be produced.

At ATL, that process can move much faster because the relevant decision-makers and subject matter experts are available in-house.

In one recent example, updated CAD data was received on a Monday. That same day, the team designed the mold tool for 3D printing.

On Tuesday, the mold was fitted into a standard bolster and initial trials began.

By Wednesday, the required modifications had been made based on trial results, and the parts were molded.

On Thursday, the final parts were assembled, packaged, and shipped to the customer.

The customer received fully representative parts based on the updated CAD models within the same working week.

That speed was not the result of bypassing process.

It was the result of having the right process, expertise, and capability connected.

Faster Feedback, Not Just Faster Parts

The ability to produce parts quickly is valuable, but the real benefit is faster learning.

With in-house tooling and injection molding capability, ATL can produce injection molded parts using production-representative materials and realistic process parameters.

In some cases, fully functional parts can be shipped within the same working week.

That matters because early access to functional, representative parts allows teams to:

• validate design assumptions earlier
• identify manufacturing risks sooner
• evaluate fit, form, and function with greater confidence
• make informed decisions before committing to steel tooling

The primary benefit is not speed for its own sake.

It is reducing uncertainty earlier in development.

Maintaining Compliance While Iterating

Agile execution only works in regulated development when it remains connected to the formal development process.

That means design changes still need to be assessed, documented, and traced.

Iteration must remain tied to:

• design inputs
• risk management
• design outputs
• verification planning
• validation strategy
• formal review processes

This is where Agile and waterfall can work together.

Waterfall provides the controlled framework required for compliance. Agile provides the rapid feedback loops that help teams make better decisions within that framework.

Conclusion: Controlled Iteration Reduces Risk

Agile development and regulatory compliance are not opposing forces.

They become difficult to reconcile only when Agile is treated as a replacement for structure rather than a method for learning within it.

In regulated medical device development, the goal is not uncontrolled speed. The goal is controlled iteration that reduces risk, improves decision-making, and keeps development moving.

By embedding Agile execution within a structured waterfall framework—and supporting it with in-house design, tooling, manufacturing, and quality expertise—ATL helps customers accelerate development without compromising regulatory expectations.

Series Conclusion

This article concludes ATL’s Medical Device Development Insights series.

Across the series, we explored how medical device teams identify user needs, apply Design Thinking, evaluate usability, translate inputs into engineering requirements, and manage development within a regulated framework.

Together, these processes support a more disciplined approach to building medical devices that are not only innovative, but safe, usable, manufacturable, and aligned with real-world clinical and business needs.