Session 10 — Polish Your Project

Duration: 75 min · Format: live online · Ages: 12–15

Session goal: by the end, students can run a refine loop on their project, make concrete improvements to their two weakest rubric rows, and re-score to prove the work got better.

Before class — prep (5 min)

• Have the refine-loop diagram below ready to share on screen.
• Ask students to bring last session's rubric self-score (the two circled weak rows).
• Have a chart with a title and labels and a messy chart without them ready to contrast, if you can.

Agenda

0:00 · Hook (5 min)

Ask the class and take a few answers:

• "Was your project's first version rough? Whose was perfect on the first try?" (Nobody's — that's the point.)
• "What's the difference between an okay project and a winning one?"

Let them guess, then reveal: it is almost never talent — it's how many times the builder tested and improved the project. Tell them today they run that loop on their own work.

0:05 · Teach — Polishing is a loop (13 min)

Explain: great projects aren't built once — they're refined again and again.

Share this diagram:

Walk through the loop out loud:

1. Test your project (or show it to someone).
2. Find the weakest spot.
3. Improve just that one thing.
4. Repeat. Each loop makes it noticeably better.

⚠ Watch for polishing the wrong thing: students love to keep improving the part that's already good (it feels rewarding). Redirect them — the loop only helps if each pass attacks the current weakest spot, not a favourite feature.

Ask: "What's one thing you already know is the weakest part of your project? How would you test it to be sure?" (Take 2–3 answers.)

0:18 · Teach — Fix the lowest score first (12 min)

Explain: don't polish what's already great — attack the lowest-scoring rubric rows for the biggest jump. Give concrete moves per row:

• Low on results? Add more data or a clearer chart.
• Low on method? Repeat the test and write the steps precisely.
• Low on presentation? Clean up labels, tidy the code, rehearse the demo.

Key point to land: judges notice details — a chart with a title and labels, a demo that doesn't crash, a tidy report. Small fixes add up to big scores.

Ask the class: "Two projects have identical results. One has a titled, labelled chart; the other has a bare screenshot. Which scores higher, and why?" (Answer: the labelled one — it's easier to trust and understand, so it wins the presentation row.)

0:30 · Activity — Polish pass + user test (30 min)

Have students work on their own project (circulate and coach).

Part 1 — Polish pass (≈20 min). 1. Open your rubric self-score from Session 9. 2. Take your two weakest rows and make one concrete improvement to each. 3. Re-test and re-score. Did the numbers go up? 4. Do a "first impressions" check: does it look finished at a glance? Fix anything messy.

Circulate and ask: "Show me the before and after — what exactly did you change, and did the score move?"

Part 2 — User test (≈10 min). Pair students. Each one lets a partner try their project with no help while they watch silently. Write down 2 improvements from where the partner got confused.

Debrief: ask 2–3 students what surprised them when someone else used their project. Land the point: watching a real user reveals problems you can't see yourself.

1:00 · Check for understanding (8 min)

Ask these aloud or drop them in the chat. Answer key (for you):

1. What is the refine loop? → Test → find the weak spot → improve → repeat.
2. Which part should you polish first? → Your lowest-scoring rubric row — that's where you gain the most.
3. Name one small detail judges notice. → A chart title/labels, a demo that works, tidy code, or a clean report (any one).

1:08 · Wrap-up + homework (7 min)

• Ask one student to name the single improvement that moved their score the most today.
• Homework — One more loop: run the refine loop one more time on your project before next session, and write one sentence on what you improved and why. Next session you write it all up.

Teaching notes

• Correct this misconception: "Polish means making the good parts even better." Reframe as attack the weakest spot each loop.
• Fast finishers (extension): push for reproducible, rigorous work — could a stranger rebuild the result from their notes? Have them clean up code, label data, write exact steps, repeat experiments to increase sample size, and report uncertainty honestly. Then finalise report, visuals, and a backup of everything.
• Low-tech fallback: if a student can't re-run their build live, have them polish the report and visuals instead — titles, labels, and clear steps still raise the rubric score.

Vocabulary

Resources

• Canva / Google Slides — make visuals clean and pro.
• Google Sheets — turn results into clear charts (with titles!).
• Tinkercad / Colab — refine a build or model.

Next session

Session 11 — Write It Up & Peer Review: students write their project report like a real paper, then trade honest feedback in a structured peer-review round.