Element K: Reflection on the Design Project

Week 11: Reflection on the Design Project

PLTW Element K — Reflection on the Design Project.

Technical Debt & Bug Post-Mortem

• As a team, list the known technical debt and open bugs in your MVP. Be honest — a Critical Design Review that only lists successes isn’t useful evidence for Element K.
• For each item, note: what caused it, whether it’s a Sprint 4 (redesign) priority or a quick fix, and what you’d do differently.

Individual Reflection

Each team member writes a short reflection covering:

• What role did you actually play across Sprints 1-3 (not just your assigned role — what you did)?
• What’s one technical or process skill you grew the most in?
• What’s one thing you’d change about how you worked with your team?

Team Reflection

• As a team, discuss what worked and what didn’t across Sprints 1-3: problem definition, literature review, PRD, mentor engagement, MVP build, and testing.
• Identify the single biggest risk heading into the redesign iteration (Sprint 4).

Finalize the Sprint 1-3 Portfolio

• Consolidate all Sprint 1-3 deliverables (PRD, decision matrix, BOM, test data, mentor logs, external evaluation) into a single, navigable engineering portfolio section.
• This portfolio is what gets defended at N@tM next week — treat this as the deadline, not Week 12.

Core Deliverables

• Technical debt / bug post-mortem.
• Individual reflections (one per team member).
• Team reflection notes.
• Finalized Sprint 1-3 portfolio.

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