Introduce XP Practices to a Legacy E-Commerce Codebase
Overview
What this challenge is about.
Run a 6-week intervention with the 7-person checkout team. Week 1: baseline (current test coverage, defect-escape rate, story cycle time). Weeks 2-5: introduce TDD on all new code via mob-programming sessions, pair-programming rotations, and weekly refactoring sessions on the worst-scoring class per static analysis. Week 6: re-measure baseline plus a team-satisfaction survey. Deliver a 6-page intervention report covering metrics, team feedback, what scaled and what didn't, and a scale-out recommendation for the other 4 product teams.
The Brief
What you'll do, and what you'll demonstrate.
Introduce TDD, pair programming, and refactoring discipline to a legacy team in 6 weeks and produce honest evidence on whether to scale it.
Earning criteria — what you'll demonstrate
- Apply XP practices to a real legacy codebase, not a greenfield project
- Measure the impact of practice changes on engineering metrics honestly
- Coach a team into pair programming and TDD without coercion
- Recommend scale-out (or not) based on evidence, not enthusiasm
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.