Sprint 4 Retrospective & Team Realignment

1 min read • Assignment

Week 16: Sprint 4 Retrospective & Team Realignment

Reflect on the Redesign

As a team, discuss Weeks 13-15: the revised problem statement, the FMEA, and the revised PRD.

Did the root-cause analysis actually change your direction, or did you end up rebuilding the same thing with different words? Be honest — this matters for Sprint 5.
What’s the single riskiest FMEA item (highest RPN) you’re carrying into the Sprint 5 build?

Reset Team Norms & Technical Ownership

Trimester 1 revealed real information about who’s strong where. Revisit your team norms and technical ownership roles from Sprint 1 and adjust them for the Beta build.
Update your Kanban board’s role/assignment structure to reflect this.

Set Knowledge Goals for the Rest of the Iteration

Each team member identifies one technical skill gap (surfaced during Trimester 1) they want to close during the Sprint 5 build.

Core Deliverables

Sprint 4 retrospective notes.
Updated team norms / technical ownership assignments.
Individual knowledge goals for Sprint 5.

Submit Assignment

Need to update a submission later? Open the submissions dashboard.