Agile Sprint Planning for an E-Health Platform Migration

FreeVerified credential2 weeksIntermediate

Overview

What this challenge is about.

Plan Sprints 0-3 for a HealthTech platform migration as a Scrum Master. Manage dependencies and velocity to earn a verifiable certificate.

The scenario

Healthcare digitization in Europe is accelerating, driven by regulations like Germany's DiGA (Digital Health Applications) framework and the European Health Data Space initiative. A regional hospital network in North Rhine-Westphalia is migrating from a legacy on-premise electronic health record (EHR) system to a cloud-based platform. The migration involves 3 hospitals, 1,200 staff users, and 15 years of patient data — all while maintaining continuous clinical operations and strict data protection compliance under both GDPR and German health data regulations (PDSG). The project has been assigned a cross-functional team of 14 people including developers, a clinical informatics specialist, a data migration engineer, and a project manager. The hospital CIO has mandated an agile approach with 2-week sprints over a planned 6-month migration window.

CredentialBlockchain-anchored

ShareableLinkedIn-ready

LanguageEnglish

PaceSelf-paced

The Brief

What you'll do, and what you'll demonstrate.

Create a detailed agile sprint plan for the first 3 months (6 sprints) of the EHR migration, including user stories with acceptance criteria, sprint goals, capacity planning, risk-adjusted velocity projections, and a Definition of Done that incorporates clinical safety and regulatory compliance requirements.

Program Fit

Where this fits in your program.

Sharpens the same skills your degree expects you to demonstrate.

Aligned coursework coming soon.

Skills

Skills you'll demonstrate.

Each one shows up on your verified credential.

Careers

Career paths this challenge builds toward

Completing this challenge demonstrates skills that transfer directly to these roles:

Career paths this builds toward

Canonical roles

Scrum Master
A scrum master holds the space where a software team becomes good at delivering software together. The role is less about ceremonies — though you'll run plenty — and more about noticing what's getting in the way and quietly removing it. Some days that means coaching an engineer through a stuck conversation; other days it means redrawing the burndown chart so a stakeholder understands what's actually achievable this sprint. Tools like Azure DevOps and Jira are scaffolding; the substance is in how you ask questions and where you choose not to intervene. Students drawn here usually care about people and process in equal measure. Growth comes from coaching real teams through real friction, then earning the credibility to challenge what they assumed was fixed.
Engineering & IT

One more thing

You can put a credential on your CV by Friday.

Start this challenge