Element C (Iteration 2): Justify Revised Design Requirements

Week 15: Justify Revised Design Requirements

PLTW Element C, Iteration 2 — Presentation and Justification of Solution Design Requirements, revised to industry grade.

Revise the PRD

• Take your Sprint 1 PRD and tighten every metric to an industry-grade standard — the kind of spec a real engineering team would be held to, not a rough first-pass target.
• Every metric must remain quantifiable (e.g. “reduce false-negative rate from 12% to under 3%,” not “improve accuracy”).

Justify Every Change

• For each revised metric, cite the evidence driving the change: an FMEA failure mode (Element B), external evaluation feedback (Element J), or mentor input.
• A metric with no cited justification is a metric to cut or reconsider.

Peer Review

• Trade your revised PRD with another team, same as Sprint 1’s peer review.
• Have them specifically check: is every metric measurable with your team’s actual tools and remaining timeline? Flag anything that looks unfeasible.

Core Deliverables

• Revised, industry-grade PRD with quantified metrics.
• Justification for each metric change, tied to FMEA/evaluation evidence.
• Peer review notes from the partner team.

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