Planning a Digital Project

Active learning works for this topic because planning a digital project benefits from collaborative dialogue and concrete outputs. Students clarify their thinking when they articulate problems, defend choices, and respond to feedback in real time. Hands-on activities move abstract ideas into structured plans that students can refine through iteration.

• JC 2
• Computing
• 4 activities
• 25 min–45 min

Learning Objectives

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

⏱ 30 min·Pairs

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.

Prepare & details

What problem are we trying to solve with our project?

Facilitation Tip: During Brainstorm Pairs, circulate and ask guiding questions like, 'Who is the user who feels this problem the most?' to keep pairs focused on audience needs.

⏱ 45 min·Small Groups

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.

Prepare & details

Who is our project for, and what do they need?

Facilitation Tip: In Small Groups, provide a blank matrix template and model how to compare features by asking, 'Which feature solves the biggest part of the problem for the user?'

⏱ 40 min·Whole Class

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.

Prepare & details

What are the main features our project should have?

Facilitation Tip: For the Project Goal Pitch, set a strict 90-second timer to encourage concise, persuasive explanations that prioritise user impact.

⏱ 25 min·Individual

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.

Prepare & details

What problem are we trying to solve with our project?

Facilitation Tip: When students create User Persona Sketches, require a name, age, and a specific goal to ensure personas feel real and relatable.

Teaching This Topic

Experienced teachers approach this topic by making planning visible and social. They avoid letting students jump straight to solutions by insisting on problem definition first. Research suggests that structured peer feedback improves project quality, so teachers rotate groups to provide fresh perspectives. Teachers also model how to say, 'No,' to unnecessary features by using real stakeholder constraints in discussions.

What to Expect

Successful learning looks like students defining a clear problem, identifying specific user needs, and justifying feature choices with evidence. They demonstrate flexibility by adapting plans based on peer input and prioritise features that balance impact with feasibility. By the end, each student should have a defensible project outline with a defined scope.

Watch Out for These Misconceptions

Common Misconception

During Brainstorm Pairs, watch for students listing ideas without connecting them to a specific user or problem. Redirect them by asking, 'Which user would want this feature, and what problem does it solve for them?'

What to Teach Instead

During Brainstorm Pairs, have students write the problem at the top of their page and then list features only if they solve that problem for a named user type.

Common Misconception

During Feature Prioritisation Matrix, watch for groups adding features because they sound impressive rather than necessary. Redirect by asking, 'If we only built three features, which ones would solve 80% of the problem?'

What to Teach Instead

During Feature Prioritisation Matrix, require groups to mark each feature with a 'must-have' or 'nice-to-have' label before scoring to force trade-offs.

Common Misconception

During Project Goal Pitch, watch for students treating feedback as optional rather than essential to improve their plan. Redirect by saying, 'After each pitch, take one piece of feedback and explain how you might adjust your plan.'

What to Teach Instead

During Project Goal Pitch, ask each group to record at least one suggestion from peers and discuss it before finalising their plan.

Assessment Ideas

Quick Check

After Brainstorm Pairs, collect each pair's problem statement and feature list. Assess whether the features directly address the problem and are tailored to the identified user types.

Peer Assessment

During User Persona Sketch, have pairs swap personas and use a checklist to assess clarity, specificity, and relevance of features to the persona's needs.

Exit Ticket

After Project Goal Pitch, ask students to write one potential feature creep issue for their project and explain why it might distract from the core problem, then identify one essential feature that must remain.

Extensions & Scaffolding

• Challenge: Ask early finishers to create a low-fidelity prototype sketch of their top three features and explain how each solves the problem for their persona.
• Scaffolding: For students who struggle, provide a partially completed problem statement or feature list to scaffold the initial brainstorm.
• Deeper Exploration: Invite students to research one existing app that solves a similar problem and compare its features to their own planned features in a short reflection.

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.