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.

• 11th Grade
• Computer Science
• 4 activities
• 25 min–45 min

Learning Objectives

1. Explain the four core principles of the Agile Manifesto.
2. Compare and contrast the roles of Product Owner, Scrum Master, and Development Team within the Scrum framework.
3. Analyze how iterative development and feedback loops reduce project risks in software development.
4. Differentiate between the four Scrum ceremonies: sprint planning, daily scrum, sprint review, and sprint retrospective.
5. Design a simple project plan using Scrum's sprint structure for a given problem.

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.

Prepare & details

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.

Setup: Groups at tables with problem materials

Materials: Problem packet, Role cards (facilitator, recorder, timekeeper, reporter), Problem-solving protocol sheet, Solution evaluation rubric

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

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.

Prepare & details

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.

Setup: Flexible seating for regrouping

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

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

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.

Prepare & details

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.

Setup: Standard classroom seating; students turn to a neighbor

Materials: Discussion prompt (projected or printed), Optional: recording sheet for pairs

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

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.

Prepare & details

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.

Setup: Wall space or tables arranged around room perimeter

Materials: Large paper/poster boards, Markers, Sticky notes for feedback

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

Teaching This Topic

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.

What to Expect

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

Common Misconception

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?'

What to Teach Instead

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.

Common Misconception

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?'

What to Teach 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.

Assessment Ideas

Quick Check

After the Mini-Sprint Simulation, present students with a scenario where a team is blocked mid-sprint. Ask them to identify which Scrum role is most relevant to unblock the team and explain why in 1-2 sentences.

Discussion Prompt

During the Think-Pair-Share: Waterfall vs. Agile Case Studies, pose the question, 'Your team is halfway through a sprint and discovers a major technical issue. How would the Scrum framework guide your team’s response during the daily standup?' Listen for mentions of the daily Scrum’s focus on impediments and the sprint goal.

Peer Assessment

After the Jigsaw: Scrum Roles, have students 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.

Extensions & Scaffolding

• Challenge early finishers to design a 3-sprint plan for their capstone project, including risk mitigation strategies for each sprint.
• Scaffolding for struggling students: Provide a partially completed sprint backlog template with example user stories to help them structure their thinking.
• Deeper exploration: Have students research and compare Scrum with Kanban, then present key differences in a 5-minute lightning talk.

Key Vocabulary

Agile	A set of software development principles emphasizing flexibility, collaboration, customer feedback, and rapid iteration over rigid, upfront planning.
Scrum	A specific, popular framework within Agile that uses short, time-boxed cycles called sprints to deliver working software incrementally.
Sprint	A fixed, short period, typically 1-4 weeks, during which a Scrum team works to complete a set amount of work and produce a potentially shippable product increment.
Product Backlog	A prioritized list of features, requirements, and tasks for the product, managed by the Product Owner.
Daily Scrum	A short, daily meeting where the Development Team synchronizes activities and creates a plan for the next 24 hours.