Teacher copy: This page may include teaching prompts or answer keys. Answer keys in this public library can be viewed by anyone. Give learners a clean prompt, use checks as formative evidence, and change a case locally when prior access matters.
Goal: separate first-version needs from unsupported features in Card D. Say: “An attractive feature is not automatically a requirement.”
0–2: State the only confirmed update capacity: workshop times weekly.
2–7: Model a first-version schedule page and mark live stock as unsupported.
7–13: Pairs sort advice, counts, bookings and translations by evidence and process needed.
13–20: Independent scope note: include, defer or exclude each proposal with one reason.
20–25: Ask which missing fact would decide whether bookings are needed.
Routes: written three-column scope table; spoken scope decision with captured evidence; movable proposal strips on the scope mat with dictated justifications. Other domains:Day 4 swaps. Optional/home: reduce a fictional feature list to a defensible first version. Move: if someone proposes publishing a translation or count “for now”, ask who will verify accuracy and keep it current.