Introduction
The core message of AAMI TIR45 is simple: Agile and regulatory rigor are not mutually exclusive. In fact, the document argues that Agile’s focus on small, verified increments can actually improve safety by surfacing defects much earlier than traditional Waterfall methods.
To achieve Agile Medical Device Software success, companies must stop viewing documentation as a “post-project” activity and start viewing it as a “per-sprint” deliverable.
Aligning AAMI TIR45 with IEC 62304
The biggest challenge is mapping the linear lifecycle of IEC 62304 (Software Development Plan -> Requirements -> Architecture -> Unit Testing) onto the circular nature of Sprints.
AAMI TIR45 suggests an increment-based documentation strategy:
- The Development Plan: This remains a foundational document, but it is updated to describe the Agile ceremonies (Sprints, Stand-ups, Retrospectives) that will be used.
- Software Safety Classification: This must be performed early. Agile allows you to refine this classification as the evolutionary design matures.
- Traceability: Instead of a giant matrix at the end, TIR45 encourages maintaining a “Living Traceability” where each User Story is linked to its risk and test case during the Sprint.
The “Living DHF”: Evolutionary Design Controls
Under FDA Agile Guidance, your Design History File (DHF) is built through evolutionary design. This means you don’t need “perfect” requirements on Day 1.
- Design Inputs: Your Backlog management process serves as the source for design inputs. As a User Story is moved into a Sprint, it is “refined” into a formal requirement.
- Design Outputs: Code, architecture diagrams, and interface specifications are produced incrementally.
- Design Reviews: Instead of one massive meeting, TIR45 suggests “Incremental Design Reviews” at the end of key Sprints or milestones.
The Role of Backlog as a Regulatory Tool
In an AAMI TIR45 environment, the Product Backlog is more than a list of features—it is a compliance tool.
- Non-Functional Requirements: Security, performance, and safety constraints must be “Stories” or “Constraints” in the backlog.
- Prioritization: Safety-critical features (Class C software) should be prioritized in early Sprints to validate the architecture before the project progresses too far.
Documentation Strategy: “Just-in-Time” but Disciplined
TIR45 introduces the concept of Continuous Compliance. You don’t write less documentation; you write it more frequently.
- Definition of Done (DoD): To satisfy TIR45, your DoD must include regulatory evidence. A story is not “Done” until the code is verified, the risk is updated, and the documented evidence in agile medtech is generated.
- Sprint Goals: Each goal should reflect not just a functional milestone but a quality milestone.
Managing Software Changes and Regressions
One of the strengths of AAMI TIR45 is how it handles managing software changes in agile medical devices. Because Agile thrives on change, TIR45 emphasizes:
- Automated Regression Testing: Essential to ensure that a Sprint 5 feature doesn’t break a Sprint 1 safety control.
- Impact Analysis: A quick, documented assessment of how a new User Story affects the existing risk profile.
Visure’s Role: The AAMI TIR45 Engine
Implementing AAMI TIR45 manually is a logistical nightmare. Visure Requirements ALM is built to bridge the “Agile-Waterfall Gap”:
- Agile-Regulatory Sync: Developers work in Sprints and Kanban boards, while Visure automatically compiles that data into the formal structures required for IEC 62304 compliance.
- Automated Traceability Matrix: As stories are completed, the traceability link between requirements, risks, and tests is updated in real-time.
- Snapshots & Baselining: Easily create a “State of the Project” snapshot at the end of every Sprint to provide a clear audit trail of the evolutionary design.
- Vivia AI Integration: Vivia helps ensure that your User Stories are specific and measurable enough to qualify as formal Design Inputs, keeping your backlog “audit-ready.”
Conclusion
AAMI TIR45 is the key to unlocking the true potential of software development in the Life Sciences. It removes the “Regulatory Brake” and replaces it with a “Quality Accelerator.” By following this guide and adopting a Continuous Compliance mindset, your team can deliver life-saving software faster, with higher quality and absolute regulatory confidence.
When your Agile ceremonies and your quality management systems (QMS) speak the same language, you don’t just develop faster—you develop better.
Check out the free trial at Visure and experience how AI-driven change control can help you manage changes faster, safer, and with full audit readiness.
