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.

• Grade 10
• Computer Science
• 4 activities
• 35 min–50 min

Learning Objectives

1. Compare and contrast the core principles of the Waterfall and Agile development methodologies.
2. Analyze the primary responsibilities and interactions of key roles within an Agile team, such as Product Owner, Scrum Master, and Developer.
3. Justify the advantages of iterative development and frequent, small releases over a single, large release in software projects.
4. Evaluate the impact of team collaboration and communication on the success of an Agile software development project.

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.

Prepare & details

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.

Setup: Open space or rearranged desks for scenario staging

Materials: Character cards with backstory and goals, Scenario briefing sheet

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

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.

Prepare & details

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.

Setup: Flexible seating for regrouping

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

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

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.

Prepare & details

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.

Setup: Flexible space for group stations

Materials: Role cards with goals/resources, Game currency or tokens, Round tracker

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

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.

Prepare & details

Differentiate between traditional waterfall and agile development methodologies.

Setup: Tables/desks arranged in 4-6 distinct stations around room

Materials: Station instruction cards, Different materials per station, Rotation timer

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

Teaching This Topic

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.

What to Expect

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

Common Misconception

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.

What to Teach Instead

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

Common Misconception

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.

What to Teach Instead

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.

Common Misconception

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.

What to Teach Instead

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

Assessment Ideas

Discussion Prompt

After Simulation: Iterative Prototyping, use the debate prompt: 'Imagine you are building a new social media app. Would you use Waterfall or Agile?' Circulate and listen for students referencing specific benefits and challenges from the simulation.

Quick Check

During Station Rotation: Team Roles Exploration, provide a scenario where requirements change mid-project. Ask students to identify which role would address the change and explain their reasoning using the role description cards at their station.

Exit Ticket

After Jigsaw: Methodology Comparison, have students write one key difference between Waterfall and Agile on a slip of paper. Then, ask them to list one responsibility of the Scrum Master and explain its importance to the team's success, referencing the simulation artifacts.

Extensions & Scaffolding

• Challenge: After Station Rotation: Team Roles Exploration, have students draft a sprint plan for a hypothetical project where roles must swap mid-sprint due to absences.
• Scaffolding: During Jigsaw: Methodology Comparison, provide a partially completed Venn diagram with key terms filled in to guide students in identifying differences.
• Deeper exploration: After Simulation: Iterative Prototyping, invite a local software developer to discuss how Agile teams handle real-world constraints like budget or timeline pressures.

Key Vocabulary

Agile Methodology	An iterative approach to software development that emphasizes flexibility, collaboration, customer feedback, and rapid releases of working software.
Waterfall Model	A sequential, linear approach to software development where each phase must be completed before the next begins, moving downwards like a waterfall.
Sprint	A short, time-boxed period, typically 1-4 weeks, during which a specific set of work is completed and made ready for review in an Agile project.
Product Owner	The role responsible for defining the product vision, prioritizing the product backlog, and ensuring the development team builds the right features.
Scrum Master	The facilitator for an Agile team, responsible for removing impediments, coaching the team in Agile practices, and ensuring the Scrum process is followed.
Product Backlog	A prioritized list of features, requirements, and tasks for the product, managed by the Product Owner, which the development team works from.