Computer Science · Grade 12

Active learning ideas

Agile Methodologies

Active learning transforms Agile methodologies from abstract theory into tangible practice. Students don’t just hear about sprints and feedback loops, they experience the tension between rigid plans and flexible adaptation firsthand. This approach builds the muscle memory needed to navigate real-world software projects where requirements shift as quickly as user needs.

• Ontario Curriculum Expectations
• CS.SE.6
• CS.PM.3

• 30–60 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Simulation Game
• 60 min · Small Groups

Simulation Game: Agile Sprint Cycle

Divide class into teams to develop a simple web app feature over two 20-minute sprints. Teams plan tasks on a digital board, code iteratively, demo progress, and hold a 5-minute retrospective. Debrief as a class on adaptations made.

Why do many startups prefer Agile over Waterfall for product development?

Facilitation Tip

For the Simulation, circulate with a timer and enforce the 10-minute sprint cutoff to reinforce timeboxing discipline.

What to look for

Pose the question: 'Why do many startups prefer Agile over Waterfall for product development?' Ask students to discuss in small groups, citing specific Agile principles and contrasting them with Waterfall's limitations for new ventures. Facilitate a brief class share-out of key arguments.

• Apply
• Analyze
• Evaluate
• Create
• Social Awareness
• Decision-Making

Activity 02

• Formal Debate
• 45 min · Pairs

Formal Debate: Waterfall vs Agile Scenarios

Assign pairs one model per real-world scenario, like a startup app or government system. Pairs prepare 3-minute arguments on suitability, then debate with evidence from Manifesto principles. Vote and discuss outcomes.

How does constant client feedback change the development timeline of a project?

Facilitation Tip

During the Debate, assign roles (Agile advocate, Waterfall advocate, client) to ensure all perspectives are represented in each scenario.

What to look for

Present students with a short project scenario (e.g., developing a new mobile app with uncertain user requirements). Ask them to write 2-3 sentences explaining how constant client feedback during development would alter the project timeline compared to a Waterfall approach.

• Analyze
• Evaluate
• Create
• Self-Management
• Decision-Making

Activity 03

• Role Play
• 50 min · Small Groups

Board Setup: Scrum Workflow

In small groups, create physical or digital Scrum boards for a mock project. Add tasks to backlog, move through 'to do,' 'in progress,' 'done' columns during timed sprints. Review blockers and velocity.

Explain the core principles of the Agile Manifesto.

Facilitation Tip

When setting up the Scrum Board, pre-print sticky notes with user stories so students focus on prioritization and estimation rather than drafting text.

What to look for

On an index card, have students list one core value from the Agile Manifesto and one principle that directly supports it. Ask them to provide a one-sentence example of how this value/principle might be applied in a classroom group project.

• Apply
• Analyze
• Evaluate
• Social Awareness
• Self-Awareness

Activity 04

• Role Play
• 30 min · Small Groups

Retrospective: Project Reflection

After a mini-project, individuals note what went well, what to improve, and action items on sticky notes. Groups cluster notes thematically and share one team action. Connect to Agile principles.

Why do many startups prefer Agile over Waterfall for product development?

Facilitation Tip

Use the Retrospective’s structured format (What went well? What could improve? Action items) to model continuous improvement.

What to look for

Pose the question: 'Why do many startups prefer Agile over Waterfall for product development?' Ask students to discuss in small groups, citing specific Agile principles and contrasting them with Waterfall's limitations for new ventures. Facilitate a brief class share-out of key arguments.

• Apply
• Analyze
• Evaluate
• Social Awareness
• Self-Awareness

A few notes on teaching this unit

Teaching Agile works best when you frame it as a mindset, not just a process. Avoid lecturing on the Agile Manifesto—instead, let students discover its values through frustration and adaptation in simulations. Research shows that hands-on role-playing builds deeper understanding than slides or readings alone. Balance structure with flexibility: provide clear constraints in activities (like time limits) but leave room for teams to define their own workflows within those boundaries.

By the end of these activities, students will articulate the differences between Agile and Waterfall, justify method choices for specific project scenarios, and apply core Agile principles in collaborative work. Success looks like teams that can adjust plans based on feedback, document their process, and explain the ‘why’ behind their decisions.

---

Watch Out for These Misconceptions

• During Simulation: Agile Sprint Cycle, watch for students who believe sprints are unstructured chaos.

  Use the sprint planning phase to highlight how teams define clear goals and deliverables upfront. Pause mid-sprint to point out how daily stand-ups and task boards maintain direction even as priorities shift.

• During Debate: Waterfall vs Agile Scenarios, listen for claims that Waterfall is always inferior.

  Have students map each scenario (e.g., bridge construction, mobile app) to a matrix of requirements stability, regulatory needs, and stakeholder availability, forcing them to defend method choices with evidence.

• During Board Setup: Scrum Workflow, watch for assumptions that Agile only works for small teams.

  Provide a large backlog and divide the class into sub-teams, each owning a component. Require them to coordinate dependencies on the board, demonstrating how Scrum scales with clear interfaces.

---

Methods used in this brief

• Simulation Game
• Formal Debate
• Role Play