Element J (Iteration 2): External Evaluation (UAT)

1 min read

Week 22: External Evaluation (User Acceptance Testing)

PLTW Element J, Iteration 2 — Documentation of External Evaluation, formalized as User Acceptance Testing.

Run User Acceptance Testing (UAT)

Recruit external participants — ideally different people than your Sprint 3 (Element J, Week 10) evaluators, to get fresh eyes — and have them use the Beta against real acceptance criteria drawn from your revised PRD.
UAT should test whether the solution meets the user’s definition of done, not just your test suite’s.

Document the Evaluation

Record participant outcomes against each acceptance criterion: pass/fail, plus qualitative notes on friction points.
Compare against your Sprint 3 external evaluation (Week 10) — did the issues raised there get resolved?

Redesign & Refine

Triage UAT findings: what’s a must-fix before the Sprint 6 defense, what’s a documented known-limitation, and what’s future work (feeds into Element K, Week 23).
File and resolve the must-fix items on your Kanban board.

Core Deliverables

UAT plan and results against revised PRD acceptance criteria.
Documented comparison against Sprint 3 external evaluation.
Triaged and resolved must-fix issues.