Agile Medical Device Software Development
- Online course
- EU and US requirements
- Intermediate - advanced
- Last updated - July 2026
Learn how to create an Agile medical device software development process in conformity with IEC 62304 during this self-paced, interactive online course.
Learn what Agile practices are and why they are a useful development methodology.
Learn key concepts from AAMI TIR 45, “Guidance on the use of Agile practices in the development of medical device software”.
Create documentation that complies with IEC 62304 throughout the software development process.
Develop skills to create an efficient and compliant Agile software development process.
Learn how to leverage tools throughout the development process and understand lean approaches to validation of software tools.
Receive downloadable documents and templates, such as:
– Medical device software development procedure based on Scrum (preview here),
– Basic software (tools) validation matrix,
– Identification of IEC 62304 deliverables as product vs conformity documentation.
Many organisations struggle when trying to implement Agile medical device software development. They chicken out and let the traditional V model undermine Agile methodology and thereby losing valuable benefits. I guess you found this video because you want to maximise the benefits of going Agile. Hello, and welcome to this short course on Agile Medical Device Software Development. I'm Christian Kaestner, Medical Device Software Course Instructor at Medical Device HQ. I have a software development background and have worked with many types of devices such as transplantation devices and wound care therapy. I've also been actively involved in the project teams authoring IEC 62304 and IEC 82304 standards. And I work as a lead auditor. This short course applies to you if you are developing medical device software and want to leverage the power of Agile practices. In this short course, you will get a basic understanding of Agile development. I will also help you understand how design controls can be achieved without an insane amount of administration and documentation. Then I want to explain the difference between information and documents. Lastly, I will share some ideas on how to establish a software development procedure for Agile development. Let's get to it and starting with a quick introduction to Agile. I met people obsessed with the proper methodology of implementing Agile principles. But please avoid getting absorbed in discussions about principles, because being rigid about what it's right or wrong about Agile is not any more helpful than being strict about documentation and asking you to use a typewriter to create physical documents. Instead, let's focus on what truly adds value to your organisation and workflow. The Agile Manifesto states, "Our highest priority is to satisfy the customer through early and continuous delivery of valuable software." Yes and no. In the medical device industry, we also need documentation, regulatory approval, compliance, and all that. But keep in mind that no documentation can compensate for non-working software. So in terms of prioritisation, valuable software is arguably more important than outstanding documentation. However, there is no conflict in aiming for both. In this short course, I will use Scrum as an example of an Agile framework to explain various concepts. The key elements of Scrum revolve around a sprint, which is a time-boxed activity. A typical sprint lasts a few weeks, but should be short enough to remain manageable and easily overseen. Despite what some believe, Scrum is a very controlled development methodology. For instance, before a new sprint is started, the development team agree on a sprint goal and plans the work that will be carried out. Once the sprint starts, the sprint goal is the focus and changes should be deferred to the next sprint. Before a sprint can begin, three key components must be in place: the product backlog, the sprint backlog, and sprint planning. The product backlog is the single source of input to the development team and is typically maintained by product owner. It is prioritised, meaning that the top work items are most desired. Please know that I'm intentionally saying work items and not requirements. This is because many other tasks could be overlooked if you only use the product backlog for requirements. For instance, the regulatory department might need help preparing specific technical documentation for a new region. Or the software architecture might need to be worked on. None of these are product requirements per se, but it's still work that needs to be done. In sprint planning, the development team reviews the selected work items and determines how to proceed with them. This can, for example, result in test planning and documentation updates. When discussing both the product and sprint backlog, it is easy to get carried away by the Agile Manifesto and prioritise the coolest software features because they are enjoyable to demonstrate. But remember, valuable medical device software is safe software that delivers an intended purpose. This means that many work items will not be visible when demonstrated, but will still be valuable. The sprint backlog contains the work items that will be completed in the next sprint to achieve the agreed-upon sprint goal. Although the sprint backlog might be adjusted, the intent is to maintain focus on the sprint goal and avoid ad hoc coding. In summary, the three first steps of the Scrum cycle offer many great references to design control. Furthermore, sprint planning offers opportunities to detail the design work before it starts. How great isn't that? There are two more great anchor points for design control activities that I have to mention: the definition of ready and the definition of done. The definition of ready defines attributes that work items must meet before being promoted to the sprint backlog for implementation. For example, if you choose to have software requirements in your product backlog, the definition of ready can include activity verifying requirements in IEC 62304. Simply put, the definition of ready can be used to review the input side of work to be done, while the definition of done is used to review the outputs. The definition of done acts as a checkpoint or acceptance criteria to determine whether tasks have been completed. This could, for example, include checking for updated design documentation and test coverage. There's much more to say about the Scrum framework. But for now, I hope you see it offers a mechanism to control design work. Speaking of control, let me say a few words on design controls and Agile frameworks. Over the years, I've heard people say that Agile practices can't be used when developing medical devices because it's uncontrolled or even the antithesis of design controls. And to be fair, it isn't always easy to understand how Agile methodologies satisfy design control requirements. Luckily, AAMI's technical report, TIR45, provides valuable thoughts on this topic. The report addresses the perceived conflict between Agile practices and regulatory requirements. TIR45 was born in 2012 and revised in 2023. The FDA recognised the 2012 version, but the 2023 version is not yet on the recognised standard list when recording this video, early 2025. I guess it's just a matter of time. Agile development methods were created due to poor match between software development and traditional project management methods. If you, for instance, develop a user interface with many user interactions, it is challenging to define all requirements before starting the work. Even if try hard, very hard, the end result might not match the expectations because stakeholders tend to change their minds when they reach the look and feel phase. In TIR45, this is stated as "Accept that customer needs and requirements are likely to change." Changing customer needs and requirements may seem trivial, but it's very painful in many organisations. Agile embraces changes, making change management integral to an Agile development process. This can be attributed to the expectation that relevant stakeholders are part of the team, making the decision process informed and efficient. Furthermore, the desire to demonstrate functionality after increments drives the need for regular and early testing and integration. What could be better than frequent testing throughout the life cycle to demonstrate that you are in control of the design work? Agile is about valuing the customer, not only by adding cool features. You also value the customer by getting the priorities right, such as implementing a foundational risk control measure before implementing cool features. Prioritising work is a way to control the design work. As mentioned earlier, the concept of done in Agile is fantastic. Simplified, it means continuously striving to define acceptance criteria for work activities at all levels. So far, you have learned about Agile concepts and the possibilities of integrating design control throughout the development work. However, one thing that can kill any enthusiastic Agile advocate is documentation. To convince others that your product is safe, there is no escape from sharing information with external parties. This is typically seen as a pile of printed paper. But please try to erase this image and focus on information sharing. I want you to concentrate on information instead of traditional documents. Because when developing software, you create a lot of information within your development tools. If properly managed, most information can be captured and maintained in your tools and exported to traditional paper or PDF documents only when needed. A word of advice: if you're copying and pasting information from one system to another, it is a clear sign of poor information management. I often see this happen due to fear of validating tools or because the QMS mandates that all technical documentation must be stored within it. If this sounds familiar, it is time to rethink your approach, as it adds no value. And copy-pasting is far from a reliable process. In summary, revisiting your information management strategy and investing in tool validation could really pay off. TIR45 has many interesting concepts and ideas, but I've chosen two concepts I find particularly useful to explore. The first concept can be called the layered approach. And this is a systematic approach to high-level planning. It describes what you intend to do at different points in time. The second approach is about assembling documents from pre-approved parts. Let's start with layers. The idea is to describe how functionality will evolve into a complete product and how and when various standards and regulatory requirements are met. I suggest looking at four layers: story, increment, release, and project. A story contains actionable work, also known as work items. Consequently, it is reasonable to establish evidence of detailed design, requirement traceability, and testing relating to the story. You could also consider integration and system testing, but saving this for the next layer might be more convenient. The layer above is the increment layer, and it consists of the stories worked on in an increment, which could be a sprint in Scrum. Compliance work will likely include integration testing and preferably system tests relevant to the increment. Multiple increments are then bundled into the release layer. You will likely work with regression testing and perhaps even more integration and system testing. This is also a good place to look for release management activities and formalising documentation. Let's assume you have captured detailed design information in work items, but have not established it in a submission-ready format. Now is an excellent time to extract and convert the information into documents such as a PDF that can be used in a submission. We will shortly return to this topic, but first, the product layer. Software products will have multiple releases because there is no bug-free software. But before ending up with numerous releases, the product layer should describe planning aspects, high-level risk management, and the relation to system-level design and requirements. The number of layers or their names is not carved in stone. If you like the idea of using layers, I suggest you describe your approach in a software development procedure and use a software development plan for project-specific adjustment, if needed. Now it's time to look at how information can be converted into documents. The idea is that we have information parts we want to convert into documentation. To honour document control principles, we should establish a mechanism to the left that results in controlled and pre-approved parts. These parts can later be assembled into documents. A workflow that includes creation, revision control, and approval of documentation parts will take you far. If all parts are under revision control and approved, the final document will likely be in good shape once established. Let's make it tangible by looking at some examples. The documentation parts can be stored as detailed design information in a ticket or as individual requirements in a requirement management system. The repository used to revision control the parts can be a ticket system, configuration management system, or requirement management system, for instance. The last step is approving the part. And in this flow, it does not mean carving it in stone or using Part 11 compliant signatures. No. This is the team approving the part. This approval can take place during, for instance, a peer review of detailed design information in response to agreed criteria in the definition of done. It can also happen during a sprint review or planning. Now it's time for the right-hand side to use parts to create documentation. Parts from the repository are collected and merged into documents. How easy is that? The steps required to achieve this are to assemble parts into documents and formalise them following your QMS procedure for document control, including the approval process and document storage. If you combine the idea of using layers and assembling documents, you would contribute to documentation in all layers. But the formalisation of documentation can be postponed to the higher layer. If you do this right, you will get high-quality documentation with a minimum of administrative burden. Nice. Now let's discuss an Agile development process. The first topic to address is the scope of your Agile process. Perhaps your immediate response is, "I want everything to be Agile," and you want to be release-ready after every sprint. But before we jump to conclusions, let's look at a few challenges with the term "release". A product release can be described as a three-step approach. It starts with a software release, followed by what I call a design release, and lastly, the product release. The main difference between a software release and a design release is that a software release only considers software functionality. Things like instructions for use, technical description, or design validation are not part of an IEC 62304 release, yet they must be included in a complete release. The difference between a design release and a product release is that the product release often involves interactions with external parties, such as the FDA or a notified body. These external interactions often take considerable time. It is worth noting that standards and guidance documents do not mention design release, but I hope you see the point in the three-step approach just described. Now let's get back to the initial question. What is the scope of your Agile activities? I believe using one of these three release steps is wise when defining the boundaries of your Agile ambitions because each step can be explained with precise inputs and outputs based on your organisation's need. So when deciding the scope of your Agile ambitions, consider suitable constraints and the duration you might need to work with. And even though one size fits most, you might end up in mixing methods for different purposes. In this short course, you have learned about the possibilities to include design controls in Scrum, how to manage information, and lastly, possibly constraints for scope of your Agile ambitions. With this information at hand, you should be equipped with some ideas on how to write a software development procedure. And when doing so, please don't fall for the temptation to write as a traditional V model procedure following IEC 62304. Such an approach would leave all projects without guidance, and that is not the purpose of a procedure. So if you want to go Agile, your procedure should define the activities and processes you want the development teams to follow. I suggest you set the developers as your primary audience for your procedures. The procedures should guide and help with activities such as sprint planning, execution, review, retrospective. To help people unfamiliar with the terminology, you could consider adding a process summary in the procedure to bridge your development approach and traditional medical device terminology. An obvious drawback on my suggested approach is that it becomes harder to demonstrate compliance with IEC 62304. But what is most valuable? A procedure that is helpful every day, or procedure that's helpful a few times a year when audited? I believe you can get both. Focus on those who are expected to read the procedure most, the developers, and provide a detailed cross-reference between the procedure and the clauses in IEC 62304 for auditing purposes. This approach should take you through most audits without problems. If you want to learn more about using Agile methods in medical device software development, I welcome you to sign up for the full online course, Agile and medical device software. The full course is similar to this short course, but much more comprehensive, with in-depth information and quizzes at the end of each topic to test your knowledge and understanding. The online course also includes a detailed software development procedure based on Scrum. At the end of the full course, you will also receive a course certificate, which many auditors would be asking for. At Medical Device HQ, we offer online courses, public classroom courses, as well as in-house training on safety, risk management, usability engineering, design control, and much more. Drop us a line at support@medicaldevicehq.com if you're interested in taking a next step.
with SOP and templates
From € 649/ seat
| Course length | approx. 6-16 hours (11 CPD points) |
Is this the right course for you?
This course is for professionals with a basic understanding of medical device software development, design controls, and IEC 62304. It is not a Scrum/Kanban certification course — the focus is on applying Agile principles in a regulated environment.
If you would like a comprehensive review of IEC 62304, please consider our other courses:
- Software for Medical Devices & IEC 62304
- SaMD – IEC 62304 & IEC 82304-1
- If you need a refresher on IEC 62304, please take a look at our free Quickstart course.
Select your course plan
ONLINE
YOU ARE HERE
€ 649
Average completion time 6-16 hours
Total video duration 4 hours
Number of quizzes 18
Final exam
Course certificate
Ask the instructor
6 months access to the course and instructor
Digital course companion
ONLINE LIFETIME
€ 749
Average completion time 6-16 hours
Total video duration 4 hours
Number of quizzes 18
Final exam
Course certificate
Ask the instructor
Lifetime access to the course and instructor
Digital course companion
IN-HOUSE TRAINING
CONTACT US
Tailored training to meet your company's needs
Course overview
It covers topics such as benefits and challenges with Agile methodologies, AAMI TIR45:2023; Guidance on the use of agile practices in the development of medical device software, pros and cons with Kanban vs Scrum, information management, change control, and most importantly, how to design an Agile development process in the medical device industry conforming to IEC 62304 Medical device software – Software life cycle processes.
This course is suitable for professionals in medical device software development who want to deepen their understanding of Agile methodologies or navigate the complexities of integrating Agile practices in a regulated environment.
The online course is made up of pre-recorded videos, quizzes, and a final exam. There is also a downloadable course companion within the course. You will receive a course certificate upon successful completion of the course
If you purchase the ‘Online’ course plan you will have access to the course for 6 months from enrolment. If you purchase the ‘Online lifetime’ course plan you will have lifetime access (conditions apply).
The course also includes a downloadable SOP and templates, such as:
– Medical device software development procedure(SOP) based on Scrum (preview here),
– Basic software (tools) validation matrix,
– Identification of IEC 62304 deliverables as product vs conformity documentation.
Course modules
- Welcome
- What you need to know
- Set your course goal completion date
- Pre-course assessment
- What is Agile?
- Agile pain points
- Customer, stakeholder and product owner
- Define the scope of your Agile process
- What is TIR45?
- The layer approach – Part 1
- The layer approach – Part 2
- Information management and sharing
- Document creation
- Definition of ‘done’ and ‘ready’
- From design inputs to outputs – Part 1
- From design inputs to outputs – Part 2
- Scrum or Kanban
- Scrum terminology – Part 1
- Scrum terminology – Part 2
- Choosing sprint backlog items
- Connect your software development process with other processes
- Documentation approaches – Part 1
- Documentation approaches – Part 2
- Dealing with signatures – Part 1
- Dealing with signatures – Part 2
- How tools can be helpful – Part 1
- How tools can be helpful – Part 2
- Validation of QMS software tools – Part 1
- Validation of QMS software tools – Part 2
- Validation of QMS software tools – Part 3
- Introduction to the process template
- Working with requirements – Part 1
- Working with requirements – Part 2
- Change management
- Pre-final exam
- Final exam
- Course evaluation
He is currently involved in the authoring of the updated IEC 62304 as part of TC 62/SC 62A, and serves as convener of TC 62/ahG9, a group tasked with finding consensus regarding the understanding of AI-related terms and concepts (e.g., ISO/IEC 22989-2) in IEC TC 62.
He has extensive experience of medical device development and, as a software developer, a strong dedication to software development. In the software domain he has worked in many roles such as software developer, project manager, auditing and quality management.
Benefits for you
Direct access to standards authors
Our courses are developed by members of the standardization committees involved at both national and international levels, ensuring you receive first-hand knowledge and insights.
You can ask our instructors questions during the online course thereby gaining exclusive up-to-the-minute information.
Self-paced and bite-sized learning
Our interactive online courses offer the flexibility to learn at your own pace. The high-quality videos are designed in bite-sized segments, making it easier to grasp and retain information.
This format provides a convenient alternative to traditional classroom courses accommodating different learning styles and preferences.
Training effectiveness and record-keeping
Participants’ knowledge is assessed through pre-training quizzes and a final exam, enabling a true measure of the training’s effectiveness.
Furthermore, we provide records, including the final exam score and course certificate, to satisfy ISO 13485 requirements, ensuring compliance and accountability.
Frequently asked questions
This course explains Agile frameworks such as Scrum and Kanban, but its main focus is on how to implement Agile principles within the specific environment of regulated medical software development. You will gain practical insights into adapting these methods for compliance and quality — not a comprehensive certification in Scrum or Kanban.
The course is not a webinar. This online course is made up of carefully scripted pre-recorded videos to maximize your learning. You can watch it as many times as you like, whenever and wherever you want. You can not download the course though, thus you will need to have an internet connection to take the course.
All in all, the average time to complete the course is 6-16 hours, but you can complete it in less time if you don’t repeat any of the lessons and have just one attempt at the quizzes. Please note, you don’t have to watch the whole course at once. In fact you can pause, resume and replay as often as you like. The only limitation is the final exam, where you will only have one shot.
If you purchase the ‘Online’ course plan you will have access to the course for 6 months from enrolment. If you purchase the ‘Online lifetime’ course plan you will have lifetime access to the course if you complete the final exam within 6 months of enrolment (conditions apply).
You need to have contact with our servers for your results to register on the final exam. If your computer for some reason has a problem and does not allow you to send the result of the final exam to our servers, we recommend that you take a photo or a “print screen” of the screen with your results. E-mail this image to us and we will investigate if you have successfully completed the exam and therefore should receive a course certificate even though the result has not been registered, or if you have to do the final exam again.
There is no pass/fail on the final exam (as long as you complete it within the time frame). Your result will be printed on the course certificate which means you can be really proud of your result if you get between 90% and 100% of the answers correct!
The course certificate is available for download after completing the final exam. All you need to do is log in to your account, go to My Courses and scroll down. You will find it under Your Course Certificates.
Yes, you can download a course companion within the online course. It contains a selection of key slides from the course and is in PDF format.
We offer a number of payment methods including credit card, GooglePay, ApplePay, PayPal, wire transfer/invoice depending on the country you are buying from. If you cannot find your country on the list at checkout or you are not given wire transfer as a payment method, you can submit your order via our invoice order form.
Yes, you can. The course is in HTML5 format which will play on any new iOS, Android or Windows devices.
If you purchase five seats for the same online course at the same time, we will give you one extra seat for free on that same course (e.g. buy 5 get 6, buy 10 get 12, etc). The free seat is assigned manually after the order has been received.
The course is personal, that means you buy a license for one person. It is also really inexpensive compared to any traditional course with the same scope. If you have more than one person needing the course, please purchase another seat on the course.
The instructor continuously participates in authoring the IEC 62304 and IEC 82304-1 standards. This ensures the instructor has access to first hand information and understanding of the meaning of the standard’s requirements. This is the highest qualification available for teaching the course.
There are no pre-requisites for this course.
Medical Device HQ is proud to be an accredited CPD provider, demonstrating our commitment to your continued professional development with high-quality training courses. A CPD record showcases your professional growth, boosts confidence in your abilities, and can be presented to management for better career opportunities. As a participant of a CPD certified course, you will receive a certificate awarding you CPD points following completion of the training.
Upon completing the course, you can claim 11 CPD hours (11 CPD points) for the online course.
Your course certificate will display the earned CPD hours.
Reviews
Sigma Lundinova AB
Innitius
3 Shape A/S
Magventure A/S
Device Quality Compliance
Baxalta Innovations GmbH - Takeda
AMTZ
Cyber Surgery
Group purchase
If you wish to purchase two or more seats on the same online course, click the ‘Buy multiple seats’ button below which will take you to the product page where you can simply enter the number of seats you require.
If you purchase three seats or more on the same online course at the same time, you will be added to the Professional Plan for free. This means a group account will be created for you that you can manage. You will be able to track the participant’s course progress from your group account and view quiz results.
It is the person that places the order who will be our single-point-of-contact and group leader for the group account. If you wish to change this to someone else later on, you can email us at support@medicaldevicehq.com.