Rescue a Stalling Scrum Team at a Series-B HealthTech
Overview
What this challenge is about.
Review 8 hours of recorded ceremonies and 3 sprints of Jira data (story sizing, carry-over rate, cycle time per story, blocker tags). Diagnose the top 3 root causes (likely candidates: oversized stories, hidden work-in-progress, unresolved cross-team dependency on the platform squad). Propose a 4-sprint remediation: concrete process changes (e.g., WIP (work-in-progress) limits on the in-progress column, story-splitting workshop, dedicated dependency-broker role) with success metrics per sprint. Deliver a written diagnosis, a 1-page remediation roadmap, and a 30-minute readout deck for the EM.
The Brief
What you'll do, and what you'll demonstrate.
Diagnose why a 9-person Scrum team's velocity has collapsed and propose a measurable 4-sprint recovery plan that does not require headcount changes.
Earning criteria — what you'll demonstrate
- Use sprint data to diagnose Scrum team dysfunctions
- Distinguish symptoms (low velocity) from root causes (oversized stories, dependencies)
- Design a phased remediation respecting team capacity and morale
- Communicate process change to a sceptical engineering audience
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
Careers
Roles this prepares you for.
Real titles. Real skill bridges. Pick the one closest to your trajectory.
Product Manager
Product managers who can read flow metrics and partner on remediation are the ones engineering teams trust with roadmap commitments.
This challenge sharpens
- agile-metrics
- stakeholder-communication
- process-design