Computer Science · 9th Grade

Active learning ideas

Introduction to Agile Methodologies

Active learning helps 9th graders grasp iterative development because they experience firsthand how small, repeated improvements lead to better results than one perfect attempt. When students physically build, test, and revise, the abstract concepts of sprints and feedback loops become concrete and memorable.

• Common Core State Standards
• CSTA: 3A-AP-19
• CSTA: 3A-AP-22

• 20–30 min
• Pairs → Whole Class
• 3 activities

Activity 01

• Simulation Game
• 30 min · Small Groups

Simulation Game: The Paper Plane Sprint

Groups have 5 minutes to design and build a paper plane (the MVP). They 'test' it, get feedback from a 'customer' (the teacher), and then have two more 5-minute 'sprints' to iterate and improve the design.

Explain the core principles of Agile development cycles.

Facilitation Tip

Before the Paper Plane Sprint, set a strict 5-minute timer for each iteration to mirror real sprint timelines and build urgency.

What to look for

Present students with a scenario describing a software project that has encountered unexpected user issues after launch. Ask them to identify which Agile principle is most relevant to addressing the problem and explain why.

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

Activity 02

• Inquiry Circle
• 30 min · Small Groups

Inquiry Circle: MVP Breakdown

Groups look at a complex app like Instagram or Spotify. They must work backward to identify what the 'Minimum Viable Product' version of that app looked like when it first launched.

Compare Agile methodologies with traditional Waterfall models.

Facilitation Tip

For the MVP Breakdown, provide a template with clear columns for features, user needs, and success criteria to keep groups focused on the MVP definition.

What to look for

Facilitate a class discussion comparing Agile and Waterfall. Prompt students with: 'Imagine you are building a bridge versus a new social media app. Which methodology would be more suitable for each, and why? Consider the predictability of requirements and the need for user input.'

• Analyze
• Evaluate
• Create
• Self-Management
• Self-Awareness

Activity 03

• Think-Pair-Share
• 20 min · Pairs

Think-Pair-Share: Feedback Loop

Students share a project they are working on. Their partner gives one piece of constructive feedback. The student must then explain how they would change their plan to incorporate that feedback in the next 'sprint.'

Analyze the benefits of iterative development for managing software projects.

Facilitation Tip

During the Think-Pair-Share Feedback Loop, explicitly model how to phrase feedback using 'I notice...' and 'I wonder...' to guide students toward constructive responses.

What to look for

Students work in small groups to outline a hypothetical 2-week sprint for a simple app feature. After drafting their sprint plan, they exchange plans with another group. Peers provide feedback on clarity of tasks, definition of MVP, and feasibility within the sprint timeline.

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

A few notes on teaching this unit

Teach Agile by having students fail early and often, then reflect on why the failure was useful. Avoid lecturing on theory—let the activities reveal Agile principles naturally. Research shows that when students experience iterative failure and guided reflection, they internalize the value of feedback and adaptability more deeply than through direct instruction alone.

Students will demonstrate understanding by explaining why the third paper plane flies farther than the first, identifying key parts of an MVP in a collaborative breakdown, and valuing feedback as a tool for improvement rather than a critique of their work.

---

Watch Out for These Misconceptions

• During the Paper Plane Sprint, watch for students who try to perfect their plane in the first iteration instead of accepting a 'good enough' version.

  After the first iteration, pause the activity and ask students to compare their planes with others. Point out that the fastest plane to complete is still valuable because it allows time for testing and improvement in the next sprint.

• During the MVP Breakdown, watch for students who treat feedback as a personal critique rather than a tool for product improvement.

  Use the Think-Pair-Share activity to reframe feedback as a standard part of the process. Have students practice giving feedback using the MVP Breakdown materials as a guide, focusing on the product rather than the person.

---

Methods used in this brief

• Simulation Game
• Inquiry Circle
• Think-Pair-Share