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.

• 9th Grade
• Computer Science
• 3 activities
• 20 min–30 min

Learning Objectives

1. Compare the iterative cycles of Agile methodologies with the linear progression of Waterfall models.
2. Analyze the benefits of incorporating user feedback loops into software development.
3. Design a sprint plan for a small software feature, identifying key tasks and a Minimum Viable Product (MVP).
4. Evaluate the effectiveness of different Agile ceremonies (e.g., daily stand-ups, sprint reviews) in facilitating collaboration.

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.

Prepare & details

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.

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

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.

Prepare & details

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.

Setup: Groups at tables with access to source materials

Materials: Source material collection, Inquiry cycle worksheet, Question generation protocol, Findings presentation template

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

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

Prepare & details

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.

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

Teaching This Topic

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.

What to Expect

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

Common Misconception

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.

What to Teach Instead

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.

Common Misconception

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

What to Teach Instead

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.

Assessment Ideas

Quick Check

After the Paper Plane Sprint, present students with a scenario where a team’s first MVP crashes on launch. Ask them to explain which Agile principle applies and how they would adjust their approach based on the scenario.

Discussion Prompt

During the MVP Breakdown activity, facilitate a class discussion comparing Agile and Waterfall. Ask students to consider the predictability of requirements for building a bridge versus a social media app and justify their methodology choice.

Peer Assessment

After the Think-Pair-Share Feedback Loop, have students exchange their MVP Breakdown templates with another group. Peers assess the clarity of tasks, definition of MVP, and feasibility of the 2-week sprint plan, providing written feedback on a provided rubric.

Extensions & Scaffolding

• Challenge: Ask students to design a second sprint that improves the same product using feedback from the first round, then compare the two MVPs.
• Scaffolding: Provide sentence stems for feedback during the Think-Pair-Share activity, such as 'One thing that worked was...' and 'One improvement could be...'.
• Deeper exploration: Introduce the concept of 'story points' by having students estimate the effort required for each task in the MVP Breakdown using a simple scale.

Key Vocabulary

Agile	An iterative approach to project management and software development that emphasizes flexibility, collaboration, and rapid delivery of functional products.
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.
Minimum Viable Product (MVP)	The version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort.
Feedback Loop	A process where the outputs of a system are fed back into the system as inputs, allowing for adjustments and improvements based on user input or performance data.
Waterfall Model	A traditional, linear project management approach where progress flows downwards through distinct phases like requirements, design, implementation, verification, and maintenance.