Computer Science · 9th Grade · Collaborative Software Development · Weeks 28-36

Introduction to Agile Methodologies

Students will learn about iterative processes and feedback loops in software project management.

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

About This Topic

Agile development cycles introduce students to the iterative way modern software is built. Instead of trying to build a perfect product all at once, 9th graders learn to use 'sprints' to create a Minimum Viable Product (MVP) and then improve it based on feedback. This aligns with CSTA standards for using an iterative process to plan the development of a program.

This topic emphasizes the importance of user feedback and flexibility. Students learn that a project's direction can, and should, change as they learn more about what the user needs. This collaborative, fast-paced approach mirrors the work environment of top tech companies. Students grasp this concept faster through simulations where they must adapt their project to 'surprise' user feedback mid-development.

Key Questions

1. Explain the core principles of Agile development cycles.
2. Compare Agile methodologies with traditional Waterfall models.
3. Analyze the benefits of iterative development for managing software projects.

Learning Objectives

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

Before You Start

Introduction to Programming Concepts

Why: Students need a foundational understanding of what software is and how it is built to grasp the context of development methodologies.

Basic Project Planning

Why: Familiarity with breaking down tasks and setting simple goals is helpful before learning about structured project management approaches like Agile.

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.

Watch Out for These Misconceptions

Common Misconception

The goal is to get it right the first time.

What to Teach Instead

In Agile, the goal is to get a 'good enough' version out quickly so you can learn from it. The 'Paper Plane' activity shows that the third version is almost always better than the first.

Common Misconception

User feedback is a sign of failure.

What to Teach Instead

Feedback is the most valuable tool for improvement. Peer review sessions help students see feedback as a 'feature' of the development process, not a bug.

Active Learning Ideas

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.

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.

30 min·Small Groups

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

20 min·Pairs

Real-World Connections

• Software development teams at companies like Google and Microsoft use Agile methodologies to build and update applications such as Google Maps or Windows, releasing new features incrementally based on user testing and feedback.
• Game development studios, including Blizzard Entertainment, employ Agile sprints to create and refine video games, allowing them to adapt to player feedback and market trends throughout the development cycle.
• Startups developing new mobile apps often use Agile principles to quickly build an MVP, test it with early adopters, and iterate based on user reviews and analytics before a wider launch.

Assessment Ideas

Quick Check

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.

Discussion Prompt

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

Peer Assessment

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.

Frequently Asked Questions

What is a 'sprint' in Agile?

A sprint is a short, set period of time (usually 1-4 weeks) during which a specific set of work must be completed and made ready for review.

What is a Minimum Viable Product (MVP)?

An MVP is the simplest version of a product that still works and provides value to the user. It allows a team to test their ideas quickly without spending too much time or money.

Why is Agile better than the 'Waterfall' method?

The Waterfall method is linear and doesn't allow for changes once a project starts. Agile is flexible and allows teams to respond to problems or new ideas as they happen, which usually leads to a better final product.

How can active learning help students understand Agile?

Agile is a 'learning by doing' philosophy. By participating in short, timed 'sprints' in class, students feel the rhythm of iterative development. This hands-on experience teaches them to manage their time and prioritize features more effectively than any lecture on project management could.