Computational Thinking Project · Semester 2

Project Presentation and Review

Communicating technical solutions to stakeholders and reflecting on the development process.

About This Topic

Project Presentation and Review prepares JC 2 students to communicate their Computational Thinking Projects effectively to diverse audiences. They practice translating technical elements, like algorithmic logic, data flows, and error-handling strategies, into clear narratives using visuals, demos, and analogies. Students tackle key questions: simplifying complex ideas for non-experts, detailing hurdles such as debugging interdependent modules overcome via systematic testing, and outlining scalability through optimized code or cloud integration for larger user loads.

This topic strengthens MOE curriculum goals by blending computational thinking with essential soft skills like articulation and self-assessment. Reflections encourage students to evaluate their use of abstraction or pattern generalization, recognize team contributions, and plan future improvements, mirroring real-world software development cycles.

Active learning excels here with structured peer critiques and iterative rehearsals, turning passive delivery into interactive exchanges. Students gain confidence handling tough questions, refine content based on immediate feedback, and internalize reflection through shared discussions, ensuring skills transfer to exams and careers.

Learning Objectives

• Explain the core logic and technical design choices of their Computational Thinking Project to a non-technical audience.
• Analyze the most significant technical challenges encountered during project development and articulate the strategies used to resolve them.
• Evaluate the strengths and weaknesses of their project's architecture in relation to scalability and potential future enhancements.
• Synthesize feedback received during project review sessions to propose specific improvements for their solution.

Before You Start

Project Planning and Design

Why: Students need to have a defined project scope and initial design to be able to present and review it.

Algorithm Design and Analysis

Why: Understanding how algorithms work is fundamental to explaining their logic and discussing technical hurdles.

Data Structures

Why: Knowledge of data structures is necessary to discuss how data is organized and managed within their project, especially when considering scalability.

Key Vocabulary

Stakeholder	An individual or group with an interest in the outcome of a project, such as a client, end-user, or manager, who may not have technical expertise.
Technical Debt	The implied cost of rework caused by choosing an easy (limited) solution now instead of using a better approach that would take longer. This can manifest as code that is hard to maintain or extend.
Scalability	The ability of a system, network, or process to handle a growing amount of work, or its potential to be enlarged to accommodate that growth.
Abstraction	The process of hiding complex realities while exposing only the essential features. In this context, it means simplifying technical details for a non-technical audience.

Active Learning Ideas

Role-Play: Stakeholder Q&A

Pair students as presenter and non-technical stakeholder. Presenter pitches project in 5 minutes; stakeholder asks clarification questions. Switch roles and discuss adaptations needed. End with peer feedback on clarity.

⏱ 35 min·Pairs

Generate mission

Reflection Carousel: Hurdle Analysis

Post student reflections on hurdles around the room. Small groups rotate every 7 minutes, reading and adding sticky notes with solution suggestions or questions. Debrief as a class on common themes.

⏱ 45 min·Small Groups

Generate mission

Scalability Workshop: Scenario Challenges

Provide groups with scaled-up user scenarios for their projects. Brainstorm and prototype one scalability fix, like refactoring algorithms. Groups share prototypes in a 2-minute pitch to the class.

⏱ 30 min·Small Groups

Generate mission

Pitch Relay: Team Refinement

Whole class forms a circle. Each student gives a 1-minute project summary; next refines it with one improvement. Continue until all contribute, highlighting collective enhancements.

⏱ 40 min·Whole Class

Generate mission

Real-World Connections

Software engineers at Google present new feature proposals to product managers and marketing teams, translating complex algorithmic changes into user benefits and business impact statements.

Data scientists at a financial institution explain predictive models to regulatory bodies, focusing on the outcomes and risk mitigation rather than the intricate statistical methods used.

Watch Out for These Misconceptions

Common Misconception

Technical jargon impresses all audiences.

What to Teach Instead

Non-experts disengage without relatable terms. Role-play activities let students test language live, observe confusion, and practice analogies, building audience awareness through trial and adjustment.

Common Misconception

Reflection lists steps taken, not lessons learned.

What to Teach Instead

Surface descriptions miss growth opportunities. Carousel reviews prompt peers to probe 'why' choices worked, guiding deeper analysis and revealing process insights via collaborative dialogue.

Common Misconception

Scaling solutions focus only on adding servers.

What to Teach Instead

Efficiency in algorithms and data structures matters more. Scenario workshops expose this through group ideation, where debates clarify holistic approaches over simplistic fixes.

Assessment Ideas

Peer Assessment

Students present their project demo and explanation to a small group. Peers use a rubric to assess clarity of explanation (e.g., 'Was the core problem and solution clearly stated?'), identification of technical hurdles, and suggestions for improvement. The rubric includes space for specific written feedback.

Discussion Prompt

Facilitate a whole-class discussion using prompts like: 'What common patterns did you observe in how students explained complex algorithms?' or 'Which project faced the most unexpected challenge, and what was the key learning from overcoming it?'

Exit Ticket

Ask students to write on an index card: 'One technical concept I struggled to explain to a non-technical person was _____, and I would simplify it by _____. The biggest technical hurdle I overcame was _____, and the solution involved _____.'

Frequently Asked Questions

How do students simplify algorithms for non-technical audiences?

Use everyday analogies, like comparing sorting algorithms to organizing a bookshelf, and visuals such as flowcharts or app demos. Practice with mixed-ability pairs acting as stakeholders helps students identify confusion points early. Limit jargon, focus on problem-solving outcomes, and invite questions to confirm understanding, aligning with MOE's communication standards.

What prompts guide effective project reflections?

Ask: 'What assumption failed and why?', 'How did computational thinking strategies help overcome hurdles?', and 'What changes for 10x users?'. These target analysis over description. Shared reflection carousels encourage peer input, deepening insights and modeling professional post-mortems in 60-70 words of structured response.

How can active learning improve presentation and review skills?

Role-plays and peer feedback loops simulate real stakes, helping students adapt on the fly and build resilience. Carousel walks and pitch relays foster collaboration, turning solo prep into group refinement. These methods make abstract skills tangible, boost engagement, and mirror industry practices, with debriefs reinforcing metacognition for lasting gains.

How to assess project presentations fairly?

Use rubrics weighting clarity (40%), technical accuracy (30%), reflection depth (20%), and Q&A handling (10%). Video recordings allow self-review alongside peer scores. Align with MOE standards by noting scalability ideas and hurdle analysis. Provide models first, then calibrated group grading to ensure consistency across diverse projects.