Assessment plan:

Learning Outcomes:

  1. Apply basic coding concepts in Sprite Lab (like using loops, events, functions, and variables).
  2. Show creativity in making sprites move, animate, or interact.
  3. Demonstrate persistence by trying, testing, and adjusting code if even challenges arise. Show a problem solvers mindset.
  4. Reflect on their coding process (what worked, what they learned).

Formative Assessment:

  • Observation & Check-ins:
  • During the activity, we can check in and ask students guiding questions like:
  • “What is your sprite doing right now?”
  • “Why did you choose this block?”
  • “What happens if you put it in a loop?”

– The Purpose: We can catch misconceptions early and also give encouragement.

– Mini-Showcase:

– We could also pause halfway and let 2–3 volunteers quickly “show & tell” what their sprite does.

– Encourage peers to ask 1 question or give 1 idea.

– Feedback Style:
Immediate, verbal, positive, and suggestive

Summative Assessment (end of the activity)

Each student will present or share their Sprite Lab project. They will be assessed on the following:

  • Core Coding Concepts (40%)
    The project should use at least one loop, include an event (such as a key press or click), and create some kind of animation or interaction.
  • Creativity and Problem Solving (30%)
    The sprite should demonstrate some unique behavior, such as dancing, talking, or moving in an interesting way. Students are encouraged to experiment with different blocks or functions beyond the bare minimum.
  • Completion and Effort (20%)
    The project should run without breaking. Students should also demonstrate that they tested or debugged their work.
  • Reflection (10%)
    Students will provide a quick written or verbal response to a prompt such as: “What did you learn while making this?” or “What would you add if you had more time?”

Proficiency Rating

Final standing can be determined in one of two ways:

  • Complete / Incomplete (simple pass/fail)
  • Proficiency Scale:
    • 4 – Exceeds: Uses multiple coding concepts, includes creative interactions, and provides a strong reflection.
    • 3 – Meets: Meets the minimum coding requirements, shows effort, and provides a short reflection.
    • 2 – Developing: Partial attempt, sprite moves but missing key coding blocks.
    • 1 – Beginning: Did not finish or only completed minimal work.

Confidence in Outcomes

Since students are asked to demonstrate their project live, the confidence level in determining whether they have met the outcomes is high. Watching their sprite in action and hearing their reflection provides clear evidence of:

  • Understanding of loops and events (directly observable in the code).
  • Engagement and effort (observable in the project’s behavior and polish).

While creativity scoring has some subjectivity, the combination of coding, completion, and reflection criteria ensures a fair and balanced assessment