Computer Science · 11th Grade

Active learning ideas

Agile Methodologies and Scrum

Active learning works well for Agile and Scrum because these concepts are best understood through doing, not just listening. Students need to experience the rhythm of sprints, the pressure of deadlines, and the collaboration required in daily standups to truly grasp why Agile is structured the way it is.

• Common Core State Standards
• CSTA: 3B-AP-18
• CSTA: 3B-AP-20

• 25–45 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Collaborative Problem-Solving
• 45 min · Small Groups

Mini-Sprint Simulation

Teams receive a backlog of small tasks for a fictional app feature and run a 5-minute sprint planning, then spend 25 minutes building (sketching wireframes or writing pseudocode), followed by a 10-minute sprint review and a 5-minute retrospective. The debrief focuses specifically on what changed from the original plan to what was actually completed.

Explain the core principles of Agile development and the Scrum framework.

Facilitation Tip

During the Mini-Sprint Simulation, set a visible timer and enforce the 15-minute daily standup limit to create urgency and mimic real-world constraints.

What to look for

Present students with a scenario describing a project challenge. Ask them to identify which Agile principle or Scrum role is most relevant to addressing the challenge and explain why in 1-2 sentences.

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

Activity 02

• Jigsaw
• 40 min · Small Groups

Jigsaw: Scrum Roles

Divide the class into three groups, each researching one Scrum role: Product Owner, Scrum Master, or Developer. Each group creates a one-page role card covering responsibilities, common anti-patterns, and a decision scenario. Groups then re-form into mixed teams where each person teaches their role using the card.

Analyze how iterative development reduces the risk of project failure.

Facilitation Tip

For the Jigsaw: Scrum Roles, assign each expert group a different Scrum role and require them to prepare a 2-minute pitch explaining their role’s responsibilities and why it matters.

What to look for

Facilitate a class discussion: 'Imagine your team is halfway through a sprint and discovers a major technical issue that will prevent completing the planned work. How would the Scrum framework guide your team's response during the daily standup and the sprint review?'

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

Activity 03

• Think-Pair-Share
• 25 min · Pairs

Think-Pair-Share: Waterfall vs. Agile Case Studies

Present two real project outcomes -- one Waterfall project that failed due to late requirement changes and one Agile project that succeeded through iteration. Students individually identify the key decision points, then pair to compare analyses before sharing conclusions with the whole class.

Differentiate between roles and ceremonies within a Scrum team.

Facilitation Tip

In the Think-Pair-Share: Waterfall vs. Agile Case Studies, provide printed case studies with clear red flags for traditional planning so students can physically highlight differences during their analysis.

What to look for

Students work in small groups to outline a hypothetical 2-week sprint for their capstone project. They then present their sprint goal and backlog to another group. Peers assess the clarity of the goal and the realism of the backlog items, providing one suggestion for improvement.

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

Activity 04

• Gallery Walk
• 30 min · Small Groups

Gallery Walk: Retrospective Formats

Post four retrospective formats around the room -- Start/Stop/Continue, 4Ls, Mad/Sad/Glad, and the Sailboat -- each applied to the same shared class scenario. Groups rotate and try each format, then the whole class discusses which format fits which type of situation based on what they experienced.

Explain the core principles of Agile development and the Scrum framework.

Facilitation Tip

During the Gallery Walk: Retrospective Formats, hang printed retrospective templates at stations so students can annotate them directly with sticky notes to show their understanding of each format’s purpose.

What to look for

Present students with a scenario describing a project challenge. Ask them to identify which Agile principle or Scrum role is most relevant to addressing the challenge and explain why in 1-2 sentences.

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

A few notes on teaching this unit

Experienced teachers approach this topic by linking theory to immediate, tangible experiences. They avoid lecturing about Agile values and instead let students feel the pain of poor planning during simulations. They also emphasize the difference between Scrum roles through role-play, because abstract definitions don’t stick as well as seeing a Scrum Master in action. Research suggests that active learning doubles retention for these concepts, especially when students reflect on their mistakes in real time.

By the end of these activities, students should confidently explain Scrum roles, plan a sprint, and distinguish Agile from traditional approaches. They should also be able to identify when Agile practices would have improved a hypothetical project’s outcome.

---

Watch Out for These Misconceptions

• During the Mini-Sprint Simulation, watch for students assuming Agile means no planning. After the simulation, debrief by pointing to the sprint backlog and asking, 'Where did your team plan? When did you adjust?'

  During the Jigsaw: Scrum Roles, redirect students who confuse the Scrum Master with a manager by having them role-play both positions. The Scrum Master should facilitate a standup while the ‘manager’ assigns tasks, making the difference in approach immediately visible.

• During the Jigsaw: Scrum Roles, watch for students assuming the Scrum Master assigns tasks. After the role-play, ask the class, 'Who decided the tasks? What did the Scrum Master do instead?'

  During the Gallery Walk: Retrospective Formats, clarify the difference by having students write one sentence on each template describing its purpose before moving to the next station. Stop the class to share out and correct any blurring of review and retrospective.

---

Methods used in this brief

• Collaborative Problem-Solving
• Jigsaw
• Think-Pair-Share
• Gallery Walk