Computer Science · Grade 10

Active learning ideas

Agile Methodologies and Team Roles

Active learning works for Agile Methodologies because students need to experience teamwork, adaptability, and iterative problem-solving firsthand. When they step into roles like Product Owner or Scrum Master, they see how planning and feedback shape outcomes, making abstract concepts tangible.

• Ontario Curriculum Expectations
• CS.HS.D.5
• CS.HS.D.6

• 35–50 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Role Play
• 45 min · Small Groups

Role-Play: Agile Team Sprint Planning

Assign roles: product owner presents backlog, scrum master times discussion, developers estimate tasks. Groups plan a 10-minute sprint for a mock app feature, then review what fits. Debrief on role impacts.

Differentiate between traditional waterfall and agile development methodologies.

Facilitation Tip

During Role-Play: Agile Team Sprint Planning, circulate with a timer to keep discussions focused and model how to push teams to set measurable sprint goals.

What to look for

Pose the following question to the class: 'Imagine you are building a new social media app. Would you use Waterfall or Agile? Explain your choice, referencing at least two specific benefits of your chosen methodology and one potential challenge.'

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

Activity 02

• Jigsaw
• 50 min · Small Groups

Jigsaw: Methodology Comparison

Divide class into expert groups on waterfall or agile phases. Experts teach peers via posters, then mixed groups debate pros/cons for a sample project. Vote on best method with reasons.

Analyze the responsibilities of different roles within an agile team.

Facilitation Tip

In Jigsaw: Methodology Comparison, provide a graphic organizer that forces students to contrast features side by side before discussing in expert groups.

What to look for

Provide students with a short scenario describing a software project with changing requirements. Ask them to identify which role (Product Owner, Scrum Master, Developer) would be most concerned with a specific change and explain why, referencing their responsibilities.

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

Activity 03

• Simulation Game
• 40 min · Pairs

Simulation Game: Iterative Prototyping

Pairs build a simple web page iteratively over three 10-minute sprints, incorporating 'client' feedback each time. Compare to a one-shot waterfall build by another pair.

Justify the benefits of frequent, small updates over one large final release in agile development.

Facilitation Tip

For Simulation: Iterative Prototyping, set a clear rule that each prototype version must include a testable feature to reinforce the Agile focus on working software.

What to look for

On a slip of paper, have students write down one key difference between Waterfall and Agile. Then, ask them to list one responsibility of either the Scrum Master or the Product Owner and briefly explain its importance to the team's success.

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

Activity 04

• Stations Rotation
• 35 min · Small Groups

Stations Rotation: Team Roles Exploration

Stations cover each role with scenarios and tasks: product owner backlog sort, scrum master retrospective, developer pairing. Groups rotate, noting how roles interconnect.

Differentiate between traditional waterfall and agile development methodologies.

What to look for

Pose the following question to the class: 'Imagine you are building a new social media app. Would you use Waterfall or Agile? Explain your choice, referencing at least two specific benefits of your chosen methodology and one potential challenge.'

• Remember
• Understand
• Apply
• Analyze
• Self-Management
• Relationship Skills

A few notes on teaching this unit

Experienced teachers approach this topic by starting with simulations to build intuition, then layering in theory through jigsaws and debates. They avoid overwhelming students with jargon upfront, instead letting roles emerge naturally during activities. Research suggests students grasp Agile best when they experience its core values—collaboration, responsiveness, and continuous improvement—through repeated, low-stakes iterations.

Successful learning looks like students confidently explaining the purpose of each Agile role, comparing methodologies with evidence from simulations, and justifying their choices during debates. They should demonstrate adaptability in planning and clear communication about responsibilities.

---

Watch Out for These Misconceptions

• During Role-Play: Agile Team Sprint Planning, watch for students assuming sprints are unstructured. Redirect by asking teams to point to their prioritized backlog items and daily stand-up goals on the whiteboard.

  During Role-Play: Agile Team Sprint Planning, explicitly connect planning to artifacts like the backlog and burndown charts, showing how structure enables flexibility.

• During Station Rotation: Team Roles Exploration, watch for students treating roles as rigid silos. Redirect by asking them to identify overlaps in responsibilities listed on the station cards.

  During Station Rotation: Team Roles Exploration, use the station cards to highlight how roles collaborate, such as developers consulting the Product Owner on feature clarity.

• During Jigsaw: Methodology Comparison, watch for students assuming Agile is always faster without trade-offs. Redirect by asking them to list constraints in their case studies that might slow Agile delivery.

  During Jigsaw: Methodology Comparison, use the case study details to prompt discussions about context, such as whether regulatory requirements favor Waterfall.

---

Methods used in this brief

• Role Play
• Jigsaw
• Simulation Game
• Stations Rotation