Computing · JC 2 · Computational Thinking Project · Semester 2

Planning a Digital Project

Students will learn to define the goals and features of a simple digital project, considering who it's for and what it needs to do.

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

About This Topic

Planning a digital project requires students to define clear goals and features for a simple application or tool. They identify the problem to solve, specify the target audience, and outline essential functionalities that meet user needs. This process aligns with the MOE Computational Thinking Project in Semester 2, where students apply decomposition and abstraction to break down real-world challenges into manageable digital solutions.

In the JC 2 Computing curriculum, this topic strengthens computational thinking by emphasizing user-centered design before coding begins. Students consider constraints like platform limitations and usability, fostering skills in iteration and evaluation that prepare them for the full project lifecycle. Connecting to key questions such as 'What problem are we solving?' and 'What features are essential?', it builds a structured approach to innovation.

Active learning shines here because planning involves collaboration and rapid prototyping. When students role-play as users or sketch wireframes in groups, vague ideas sharpen into feasible plans. Peer feedback sessions reveal oversights early, making the planning phase engaging and iterative, which boosts ownership and refines critical thinking before implementation.

Key Questions

1. What problem are we trying to solve with our project?
2. Who is our project for, and what do they need?
3. What are the main features our project should have?

Learning Objectives

• Analyze a given problem statement to identify the core issue a digital project aims to address.
• Design a user persona to represent the target audience for a digital project, detailing their needs and context.
• Create a feature list for a digital project, prioritizing functionalities based on user requirements and project goals.
• Evaluate the feasibility of proposed project features against potential technical and time constraints.
• Synthesize user needs, project goals, and technical considerations into a coherent project plan document.

Before You Start

Decomposition

Why: Students need to be able to break down complex problems into smaller, more manageable parts before they can define project goals and features.

Abstraction

Why: Understanding how to identify and focus on essential details while ignoring irrelevant information is crucial for defining project scope and features.

Key Vocabulary

User Persona	A fictional representation of an ideal user for a product or service. It includes demographics, goals, motivations, and pain points to guide design decisions.
Minimum Viable Product (MVP)	The version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort.
Feature Creep	The tendency for a project's requirements to expand over time, often adding unnecessary features that can delay completion and increase complexity.
Wireframe	A basic visual guide used in user interface design to represent the skeletal framework of a website or application, focusing on layout and functionality.

Watch Out for These Misconceptions

Common Misconception

Planning is just listing random ideas without user focus.

What to Teach Instead

True planning starts with audience needs and problem definition. Role-playing users in pairs helps students empathise and prioritise, turning vague lists into targeted features. Group critiques expose gaps quickly.

Common Misconception

More features make a better project.

What to Teach Instead

Quality features solve core problems efficiently. Prioritisation matrices in small groups teach students to balance scope with feasibility, preventing overload. Iterative voting refines choices collaboratively.

Common Misconception

Planning ends once goals are written.

What to Teach Instead

Planning is iterative with feedback loops. Pitch sessions to the class simulate stakeholder reviews, helping students adapt plans based on real input and build resilience.

Active Learning Ideas

Brainstorm Pairs: Problem and Audience Mapping

Pairs select a real-world problem relevant to school life, such as organising club events. They list user needs in 10 minutes, then create a simple mind map linking problems to audience profiles. Share one insight with the class.

30 min·Pairs

Small Groups: Feature Prioritisation Matrix

In small groups, students brainstorm 10 potential features for their project. They score each on importance and feasibility using a 1-5 scale matrix, then select top 5. Discuss trade-offs as a group.

45 min·Small Groups

Whole Class: Project Goal Pitch

Each group pitches their project goal and key features in 2 minutes to the class. Class votes on clarity and votes down unclear pitches. Refine based on feedback in 10 minutes.

40 min·Whole Class

Individual: User Persona Sketch

Students individually draw and describe one user persona, including needs and pain points. Swap with a partner for quick feedback, then revise. Compile into a class gallery.

25 min·Individual

Real-World Connections

• Software developers at Grab plan new features for their ride-hailing app by first defining the problem, such as reducing wait times for passengers or improving driver earnings, and then creating user personas for both riders and drivers to guide feature development.
• Game designers at Ubisoft use detailed user personas and define core gameplay loops to plan new video games, ensuring that features like character progression or multiplayer modes align with player expectations and the overall game vision.

Assessment Ideas

Quick Check

Provide students with a brief scenario describing a common problem (e.g., difficulty finding study groups, managing personal finances). Ask them to write down: 1. The specific problem they are solving. 2. Two potential user types and what they need. 3. Three essential features for a digital solution.

Peer Assessment

Students work in pairs to create a simple user persona for a hypothetical app. They then swap personas and answer these questions: 1. Is the persona detailed enough to understand the user's needs? 2. What is one feature this persona would definitely need? 3. What is one feature that might be unnecessary for this persona?

Exit Ticket

Ask students to list one potential 'feature creep' issue for a project they are considering and explain why it might be a problem. Then, have them identify one feature that is essential for the project's core purpose.

Frequently Asked Questions

How do I introduce planning a digital project to JC 2 students?

Start with a relatable problem, like designing an app for exam timetables. Guide students through key questions: problem, audience, features. Use templates for goal statements and feature lists to scaffold their first plans. This builds confidence before group work.

What tools help with digital project planning?

Simple tools like Google Jamboard for mind maps, Miro for wireframes, or even paper sketches work well. Trello boards track features by priority. Introduce one tool per activity to avoid overload, focusing on planning concepts over tech mastery.

How does active learning benefit planning digital projects?

Active methods like paired brainstorming and group pitches make planning dynamic and student-owned. Role-playing users reveals hidden needs, while peer feedback hones ideas iteratively. This approach turns abstract steps into tangible skills, increasing engagement and retention for the full project.

What are common pitfalls in student project plans?

Students often ignore user needs or add too many features. Address this with mandatory audience profiles and feasibility checks. Regular checkpoints with rubrics ensure plans stay focused and realistic from the start.