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.

• Grade 12
• Computer Science
• 4 activities
• 20 min–45 min

Learning Objectives

1. Analyze user needs and translate them into specific, measurable project requirements for a capstone.
2. Design an iterative project plan incorporating Agile principles, such as sprints and backlog management.
3. Evaluate the suitability of different technologies and development methodologies for a given capstone project scope.
4. Create a project proposal document that outlines scope, requirements, initial design, and technology choices.

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.

Prepare & details

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.

Setup: Standard classroom seating; students turn to a neighbor

Materials: Discussion prompt (projected or printed), Optional: recording sheet for pairs

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

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.

Prepare & details

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.

Setup: Flexible seating for regrouping

Materials: Expert group reading packets, Note-taking template, Summary graphic organizer

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

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.

Prepare & details

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.

Setup: Wall space or tables arranged around room perimeter

Materials: Large paper/poster boards, Markers, Sticky notes for feedback

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

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.

Prepare & details

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.

Setup: Flexible workspace with access to materials and technology

Materials: Project brief with driving question, Planning template and timeline, Rubric with milestones, Presentation materials

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

Teaching This Topic

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.

What to Expect

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

Common Misconception

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

What to Teach Instead

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.

Common Misconception

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

What to Teach Instead

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.

Common Misconception

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

What to Teach Instead

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.

Assessment Ideas

Quick Check

After the Think-Pair-Share, collect student pairs’ notes on user validation methods and review for at least two distinct methods proposed for their project context, noting whether they justify their choices with user needs.

Peer Assessment

During the Gallery Walk, have students rotate in pairs to leave feedback on three projects using the prompt: 'What is one strength of their technology choice? What is one constraint you think they overlooked?' Collect feedback to assess their ability to critique justifications.

Discussion Prompt

After the Role-Play activity, facilitate a class discussion using the prompt: 'How did the user interviews challenge or confirm your initial project assumptions?' Guide students to reference specific questions they asked and the user’s responses to assess their user-centered refinement process.

Extensions & Scaffolding

• Challenge early finishers to draft a risk register for their project, identifying three potential risks and mitigation strategies, then present these to the class.
• Scaffolding for struggling students: Provide a partially completed user story template with prompts like 'As a [user type], I want [action] so that [benefit]' to model the format before they write their own.
• Deeper exploration: Have students research and compare two Agile tools (e.g., Jira vs. Trello) for their project’s needs, then create a comparison chart to justify their choice in a 2-minute pitch.

Key Vocabulary

User Stories	Short, simple descriptions of a feature told from the perspective of the person who desires the new capability, usually a user or customer. They follow a template like 'As a [type of user], I want [some goal] so that [some reason].'
Agile Methodology	An iterative approach to project management and software development that emphasizes collaboration, flexibility, and customer feedback throughout the development lifecycle.
Minimum Viable Product (MVP)	A version of a new product that allows a team to collect the maximum amount of validated learning about customers with the least effort. It's the simplest version of the product that can be released to early adopters.
Sprint	A short, time-boxed period (usually 1-4 weeks) during which a Scrum team works to complete a set amount of work, typically a portion of the product backlog.
Backlog	A prioritized list of features, requirements, and tasks that need to be completed for a project. In Agile, it's dynamic and evolves as the project progresses.