Analysis
Rescuing a Stalled Sprint at a Boston EdTech
Overview
What this challenge is about.
Analyze the provided six-sprint dataset and interview transcripts to diagnose why sprint goals are failing. Build a quantitative view (velocity trends, scope-change rate, carryover %, defect injection) and a qualitative view (Scrum value violations, role boundary breaches). Design and document a concrete two-sprint intervention: a redesigned Sprint Planning, a structured retrospective format, PO-sales boundary protocol, and updated Definition of Done. Deliver a diagnosis report, the intervention playbook, and a recorded 10-minute video presenting findings to the CEO and squad. Success means the recommendations are specific, data-grounded, and immediately actionable.
The Brief
What you'll do, and what you'll demonstrate.
Why is a previously high-performing Scrum squad failing three consecutive sprints, and what specific interventions will restore predictable delivery?
Earning criteria — what you'll demonstrate
- Apply agile metrics (velocity, carryover, scope change) to diagnose team dysfunction
- Connect Scrum values and role boundaries to observable team behaviors
- Design and facilitate effective Sprint Retrospectives and Sprint Planning
- Translate diagnosis into concrete, measurable behavioral interventions
- Coach a Product Owner on stakeholder boundary management
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.
Career mappings coming soon.