Computer Science · Grade 12 · Software Engineering Principles · Term 4

Capstone Project Planning

Students will begin planning their capstone project, applying software engineering principles to define scope, requirements, and initial design.

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

About This Topic

Capstone project planning requires students to apply software engineering principles as they define project scope, gather requirements, and sketch initial designs. They validate solutions through user-centered methods like interviews and prototypes, create Agile-based plans for iterative work, and justify technology and methodology choices against project constraints and goals. This process directly addresses key questions on user validation, Agile integration, and decision rationale.

Positioned in the Software Engineering Principles unit (Term 4), the topic aligns with Ontario standards CS.PM.8, CS.SE.14, and CS.P.27. Students develop critical skills in project management, stakeholder analysis, and adaptive planning, which prepare them for university programs or entry-level tech roles. These elements build systems thinking by connecting requirements to feasible implementations.

Active learning benefits this topic greatly. When students collaborate on mock plans, conduct peer reviews, or simulate Agile ceremonies, they experience real-world workflows firsthand. Such approaches clarify complex principles, encourage iterative refinement, and boost ownership of their projects.

Key Questions

1. How will you validate that your solution actually meets the needs of your target users?
2. Design a project plan that incorporates Agile principles for iterative development.
3. Justify the choice of technologies and methodologies for your capstone project.

Learning Objectives

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

Before You Start

Introduction to Software Development Life Cycles

Why: Students need a foundational understanding of different project phases before planning a capstone project.

Requirements Gathering Techniques

Why: Understanding basic methods for eliciting user needs is essential for defining project requirements.

Basic Project Management Concepts

Why: Familiarity with concepts like scope, timelines, and deliverables is necessary for planning a complex project.

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.

Watch Out for These Misconceptions

Common Misconception

Project planning happens once at the start, before any coding.

What to Teach Instead

Planning evolves iteratively in Agile methods through regular reviews and adaptations. Role-playing sprints in small groups lets students see how changes arise from feedback, building flexible planning habits.

Common Misconception

User needs match the initial problem description exactly.

What to Teach Instead

Real users reveal hidden needs via direct input. Mock interviews in pairs help students practice probing questions and refine requirements, turning assumptions into validated insights.

Common Misconception

Technology choices depend only on personal familiarity.

What to Teach Instead

Selections must align with project criteria like scalability and user access. Gallery walks with peer critiques guide students to objective justifications, strengthening decision-making skills.

Active Learning Ideas

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.

20 min·Pairs

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.

45 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.

35 min·Small Groups

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.

25 min·Pairs

Real-World Connections

• Software development teams at companies like Shopify use Agile methodologies, including sprints and product backlogs, to plan and deliver new e-commerce features iteratively, responding to market changes.
• Game studios such as Ubisoft employ project managers who work with designers and engineers to define game scope, gather player feedback through prototypes, and justify technology choices for new game titles.

Assessment Ideas

Quick Check

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.

Peer Assessment

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.

Discussion Prompt

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.

Frequently Asked Questions

How do Grade 12 students validate capstone projects meet user needs?

Guide students to conduct user interviews, create low-fidelity prototypes, and run usability tests. They document findings in requirement tables linking needs to features. Follow up with peer reviews to ensure evidence-based validation, aligning with CS.PM.8 for robust project foundations.

What Agile principles fit a Grade 12 CS capstone plan?

Incorporate sprints for 1-2 week cycles, product backlogs for prioritized tasks, daily standups for progress checks, and retrospectives for improvements. Students outline these in Gantt charts or tools like Trello, justifying adaptations for solo or team work per CS.SE.14.

How does active learning support capstone project planning?

Activities like jigsaw protocols on Agile elements or gallery walks for feedback make principles experiential. Students collaborate to simulate professional workflows, iterate plans in real time, and gain confidence. This hands-on practice addresses abstract concepts directly, improving retention and application as per curriculum goals.

What are common pitfalls in capstone tech choices?

Students often pick familiar tools without considering scalability, security, or user compatibility. Teach justification rubrics covering criteria like cost and learning curve. Peer debates and checklists during planning prevent scope creep and ensure choices support standards CS.P.27.