Teacher material · Page · Unpublished in Canvas

Facilitator Guide: Picture This Day 5 — Remix, Retest, Revise, Share

Canvas state
Unpublished

TEACHER ONLY · LESSON GUIDE

Picture This Day 5 — Remix, Retest, Revise, Share

Use this page to run the lesson. The student item directly below remains the independent and absence route.

Daily Learning Contract

Topic: AI-powered project revision

Objective: Students will modify an AI-powered program, evaluate it with another user, and explain how evidence informed one revision.

TEKS:
  • §126.19(c)(2)(C) — modify and implement previously written code to develop improved programs.
  • §126.19(c)(3)(B) — discuss and implement a design process that includes planning, selecting digital tools to develop, test, and evaluate design limitations, and refining a prototype or model; and

Demonstration of learning: Working .sb3 file and a reflection naming one programmed response, one observed failure, and one revision.

Before class

Time: One class period

Student route:
Day 5 · Remix, Retest, Revise, Share

Use what already exists: Saved Day 4 project; RAISE Playground; current Day 5 rubric and submission route.

Lesson flow

  1. Launch: Reopen and test yesterday's project before changing it.
  2. Model: Model one purposeful remix and the partner-test protocol.
  3. Do: Students remix, test, revise, save, and upload their `.sb3` file.
  4. Check + support: Use the existing rubric as the check; support file saving with a visual and feedback stems.
  5. Close + handoff: Verify uploads/reflections and close with the model-versus-code distinction.

Check before students leave

Ask each student or team to point to the specific evidence named above and explain one choice, test, or revision. Completion alone is not evidence of understanding.

Support + troubleshooting

Scaffold: Keep the visual task sequence visible, assign purposeful partner roles, and use the sentence stems on the student page before simplifying the task.

When stuck: Ask students to show the exact step where the system stopped, then check setup, inputs, and saved work before replacing the task.