Computing · JC 2 · Computational Thinking Project · Semester 2

Sharing and Reflecting on Projects

Students will learn to present their completed digital projects and reflect on their learning process, challenges, and successes.

• MOE Syllabus Outcomes
• MOE: Computational Thinking Project - Middle School

About This Topic

Sharing and reflecting on projects marks the culmination of the Computational Thinking Project in JC 2 Computing. Students present their digital creations, such as apps or simulations, detailing the design process, key decisions in abstraction and algorithm selection, and real-world applications. They also articulate personal growth, including how they tackled obstacles like integrating APIs or optimizing performance through iterative testing.

This unit aligns with MOE standards by emphasizing metacognition alongside technical skills. Reflections encourage students to evaluate their use of computational thinking strategies, recognize patterns in problem-solving, and consider ethical implications of their projects. Such practices prepare them for university-level work and industry roles where clear communication of complex ideas is vital.

Active learning approaches excel in this topic. Peer gallery walks and structured feedback sessions prompt students to defend choices and absorb critiques, making abstract reflections concrete. These methods build confidence, reveal blind spots, and foster a classroom culture of constructive dialogue, ensuring deeper retention of lessons learned.

Key Questions

1. How can we effectively share our project with others?
2. What did you learn during the project development process?
3. What challenges did you face and how did you overcome them?

Learning Objectives

• Critique the effectiveness of project documentation and presentation for a given audience.
• Evaluate the personal learning journey, identifying specific computational thinking strategies applied and their impact.
• Synthesize challenges faced during project development and propose alternative solutions.
• Articulate the ethical considerations and real-world implications of their digital project.
• Defend design choices and algorithmic decisions made during project creation.

Before You Start

Project Planning and Design

Why: Students need to have experience in defining project scope, objectives, and initial design before they can reflect on the development process.

Algorithm Design and Implementation

Why: Understanding how algorithms were designed and coded is essential for students to reflect on their effectiveness and challenges during implementation.

Testing and Debugging

Why: Students must have engaged in testing and debugging to be able to reflect on the challenges encountered and the solutions implemented.

Key Vocabulary

Project Portfolio	A curated collection of a student's work, including the final project, design documents, code, and reflections, presented to showcase skills and learning.
Metacognition	The process of thinking about one's own thinking and learning, involving self-awareness of understanding, challenges, and strategies used.
Iterative Development	A project management approach where work is broken down into cycles, allowing for continuous improvement and refinement based on feedback and testing.
Audience Analysis	The process of identifying and understanding the needs, expectations, and technical background of the intended audience for a project presentation or product.
Constructive Feedback	Specific, actionable comments provided by peers or instructors aimed at improving a project or learning process, focusing on both strengths and areas for development.

Watch Out for These Misconceptions

Common Misconception

Reflection means just listing what was done, without analysis.

What to Teach Instead

Guide students to connect actions to computational thinking concepts like decomposition. Peer interviews during circles help them articulate 'why' choices worked, turning surface summaries into insightful evaluations. Active sharing reveals gaps in understanding quickly.

Common Misconception

Sharing focuses only on the final product, ignoring the process.

What to Teach Instead

Structure presentations around process stages with timelines. Gallery walks expose peers to development stories, prompting questions that highlight journey value. This shifts emphasis from perfection to resilience, common in tech fields.

Common Misconception

Challenges indicate personal failure, so hide them.

What to Teach Instead

Model vulnerability by sharing your past project struggles. Reflection prompts paired with group debriefs normalize setbacks as growth points. Students gain confidence through seeing peers' triumphs over similar issues.

Active Learning Ideas

Pecha Kucha Presentations: Project Highlights

Students prepare 20 slides advancing automatically every 20 seconds to showcase their project process and outcomes. They present to small groups, followed by 2-minute Q&A. Groups provide written feedback on one strength and one improvement area.

45 min·Small Groups

Gallery Walk: Demo Stations

Students set up stations with laptops running their projects, posters of challenges overcome, and reflection prompts. Class rotates every 5 minutes, leaving sticky notes with questions or praises. Debrief as whole class to share insights.

50 min·Whole Class

Reflection Circles: Challenge Shares

Form circles of 6-8 students. Each shares one major challenge and solution in 1 minute; others ask clarifying questions. Rotate roles so all facilitate. Conclude with personal takeaway statements.

30 min·Small Groups

Success Timeline: Group Murals

In pairs, students create timelines of their project journey on large paper, marking milestones, hurdles, and learnings. Pairs present to another pair for peer review, then display for class voting on most inspiring element.

35 min·Pairs

Real-World Connections

• Software engineers at Google present their project progress and technical designs to product managers and fellow engineers, often using slide decks and live demos to explain complex features and receive feedback.
• Game developers showcase their latest game builds at industry conferences like GDC (Game Developers Conference) to gather reactions from players and potential publishers, explaining design choices and technical hurdles overcome.
• UX/UI designers present wireframes and prototypes to stakeholders, explaining user flows and design rationale to ensure the final product meets user needs and business objectives.

Assessment Ideas

Peer Assessment

Students participate in a gallery walk of project presentations. Provide a rubric with criteria such as clarity of explanation, demonstration of project functionality, and articulation of learning. Students score 2-3 projects and provide one specific suggestion for improvement in the presentation or project itself.

Discussion Prompt

Facilitate a whole-class discussion using prompts like: 'What was the most surprising thing you learned about your own problem-solving process during this project?' and 'How did the feedback you received influence your final project decisions?' Encourage students to share specific examples.

Exit Ticket

Students complete an exit ticket answering: 'Identify one computational thinking concept you applied effectively in your project and explain its role.' and 'Describe one challenge you faced and the specific steps you took to resolve it.'

Frequently Asked Questions

How can teachers structure effective project presentations for JC 2 Computing?

Use a template with sections: project overview, computational thinking applied, challenges and solutions, demo, and future extensions. Limit to 5 minutes per student with timers. Incorporate audience roles for questions to keep engagement high. Practice runs in pairs refine delivery, ensuring clarity on technical terms for non-experts.

What reflection prompts work best for computational thinking projects?

Prompts like 'How did abstraction simplify your problem?' or 'What pattern recognition helped in debugging?' guide deep analysis. 'One skill I'll transfer to future projects' builds metacognition. Journal first, then share in pairs to refine thoughts before full presentation.

How can active learning enhance sharing and reflecting on projects?

Activities like gallery walks and pecha kucha make reflection interactive, exposing students to diverse perspectives that challenge assumptions. Peer feedback during stations provides immediate, constructive input, deepening self-assessment. Whole-class debriefs consolidate learnings, turning individual reflections into collective wisdom vital for computational thinking growth.

How to assess student reflections and presentations fairly?

Use rubrics scoring clarity of process explanation (30%), depth of challenge analysis (30%), computational thinking links (20%), and engagement (20%). Provide exemplars upfront. Peer assessment adds validity; triangulate with self-reflections. Focus feedback on growth areas to motivate continuous improvement.