Computer Science · Grade 12

Active learning ideas

Capstone Project Planning

Active learning works well for capstone project planning because students need to practice the messy, iterative process of defining scope, gathering real user input, and making technology choices. Static lectures cannot replicate the problem-solving that emerges when teams must justify their plans or adapt to feedback, making hands-on activities essential for building these professional skills.

• Ontario Curriculum Expectations
• CS.PM.8
• CS.SE.14
• CS.P.27

• 20–45 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Think-Pair-Share
• 20 min · Pairs

Think-Pair-Share: User Validation Methods

Students spend 3 minutes thinking about users for their project idea and validation strategies like surveys or prototypes. They pair up for 5 minutes to refine ideas and share examples. The whole class discusses top methods and adds them to a shared anchor chart.

How will you validate that your solution actually meets the needs of your target users?

Facilitation Tip

During the Think-Pair-Share, circulate to listen for students identifying which user validation methods (interviews, surveys, prototypes) would work best for their project context.

What to look for

Provide students with a scenario describing a common app idea (e.g., a study group finder). Ask them to write two user stories and one potential MVP feature for this app. Review responses for clarity and adherence to the user story format.

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

Activity 02

• Jigsaw
• 45 min · Small Groups

Jigsaw: Agile Planning Elements

Assign small groups one Agile aspect: sprints, backlogs, retrospectives, or daily standups. Each group researches and prepares a 2-minute teach-back with visuals. Groups jigsaw to share expertise, then apply to their capstone plans.

Design a project plan that incorporates Agile principles for iterative development.

Facilitation Tip

For the Jigsaw activity, assign roles so each group member specializes in one Agile element (sprints, backlogs, retrospectives) to ensure accountability in their expert group.

What to look for

Students share their initial project scope document. Partners review the document, answering: 'Is the scope clearly defined?' and 'Are at least three specific user needs identified?' Partners provide one suggestion for improving the clarity of the scope.

• Understand
• Analyze
• Evaluate
• Relationship Skills
• Self-Management

Activity 03

• Gallery Walk
• 35 min · Small Groups

Gallery Walk: Tech Justifications

Students post project ideas with tech choices and rationales on charts around the room. Groups rotate every 5 minutes to read, add sticky-note feedback, and note strengths. Debrief identifies common justification criteria.

Justify the choice of technologies and methodologies for your capstone project.

Facilitation Tip

During the Gallery Walk, place sticky notes with constraints (budget, timeline, user access) near each project board to guide students’ technology justifications.

What to look for

Facilitate a class discussion using the prompt: 'Imagine your capstone project requires real-time data processing. What are two potential technologies you might consider, and what are the pros and cons of each for this specific need?' Guide students to justify their choices based on project constraints.

• Understand
• Apply
• Analyze
• Create
• Relationship Skills
• Social Awareness

Activity 04

• Project-Based Learning
• 25 min · Pairs

Role-Play: Stakeholder Interviews

Pairs act as project leads and stakeholders; one asks prepared questions about needs, the other responds in character. Switch roles after 5 minutes. Debrief on effective questioning and requirement capture.

How will you validate that your solution actually meets the needs of your target users?

Facilitation Tip

In the Role-Play activity, provide a script template with open-ended questions to keep interviews focused but flexible for student adaptation.

What to look for

Provide students with a scenario describing a common app idea (e.g., a study group finder). Ask them to write two user stories and one potential MVP feature for this app. Review responses for clarity and adherence to the user story format.

• Apply
• Analyze
• Evaluate
• Create
• Self-Management
• Relationship Skills
• Decision-Making

A few notes on teaching this unit

Experienced teachers approach capstone planning by treating it as a simulation of real-world constraints, not a theoretical exercise. Avoid assigning just any project—choose one with clear user pain points so students feel the weight of real decisions. Research shows that students struggle most with balancing idealism and practicality, so provide frameworks (like MoSCoW prioritization) to ground their plans in reality. Emphasize that iteration is not failure but a core professional skill.

By the end of these activities, students will confidently defend their project plans with clear user needs, justified technology choices, and adaptable Agile frameworks. They will demonstrate this through written user stories, peer critiques, and group discussions that show iterative thinking and user-centered design.

---

Watch Out for These Misconceptions

• During the Jigsaw activity, watch for students treating Agile planning as a one-time checklist rather than an iterative cycle.

  After the Jigsaw, have groups present how their Agile elements would adapt if their project’s user needs changed mid-sprint, using their expert group notes as evidence for iteration.

• During the Role-Play activity, watch for students assuming user needs match their initial problem description without probing further.

  During the Role-Play, provide a follow-up prompt for interviewers to ask 'What challenges have you faced with [problem]?' to uncover unspoken needs, and have students reflect on these in their post-interview debrief.

• During the Gallery Walk, watch for students selecting technologies based on personal preference rather than project constraints.

  During the Gallery Walk, require each group to post their decision matrix with criteria like scalability, user access, and team expertise, then have peers add sticky-note questions challenging weak justifications.

---

Methods used in this brief

• Think-Pair-Share
• Jigsaw
• Gallery Walk
• Project-Based Learning