Computer Science · 11th Grade · Capstone Software Development · Weeks 28-36

Agile Methodologies and Scrum

Managing a project using iterative cycles and constant feedback loops.

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

About This Topic

Agile is a family of software development approaches that prioritize iterative delivery, continuous feedback, and adaptability over rigid upfront planning. Scrum is the most widely adopted Agile framework, organizing work into short cycles called sprints -- typically two weeks -- each ending with a shippable product increment. For US 11th graders in a capstone project context, Scrum provides practical structure for managing a multi-week build while learning professional practices used across the tech industry.

The core insight of Agile is that requirements change, and discovering problems early through working software is far cheaper than discovering them after months of planning. Scrum formalizes this through four ceremonies: sprint planning, daily standup, sprint review, and retrospective. Roles matter equally: the Product Owner defines priorities, the Scrum Master clears obstacles, and the development team owns delivery. Students who understand these distinctions work more effectively in collaborative build environments.

Active learning is well-suited here because Agile itself is an experiential discipline. Running a mini-sprint in class, practicing standup rituals, and retrospecting on real team friction build genuine understanding that reading a framework description cannot provide.

Key Questions

1. Explain the core principles of Agile development and the Scrum framework.
2. Analyze how iterative development reduces the risk of project failure.
3. Differentiate between roles and ceremonies within a Scrum team.

Learning Objectives

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

Before You Start

Introduction to Software Development Life Cycles

Why: Students need a basic understanding of how software is planned, built, and maintained before learning about specific methodologies like Agile and Scrum.

Team Collaboration and Communication

Why: Scrum relies heavily on effective teamwork and clear communication, so prior experience or instruction in these areas is beneficial.

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.

Watch Out for These Misconceptions

Common Misconception

Agile means no planning and no documentation.

What to Teach Instead

Agile shifts the type and timing of planning, not its absence. Teams plan at the sprint level rather than attempting exhaustive upfront project planning. Documentation exists but is lightweight and produced just in time. Students who conflate 'agile' with 'informal' tend to produce poorly coordinated team projects -- mini-sprint simulations reveal this immediately when under-planning creates rework within a single class period.

Common Misconception

The Scrum Master is the team manager who assigns tasks.

What to Teach Instead

The Scrum Master is a facilitator and obstacle-remover, not an authority figure. Task assignment is handled by the development team through self-organization. Confusing the Scrum Master with a traditional project manager is one of the most common Scrum adoption mistakes in practice. Role-play exercises that put students in each position make the distinction tangible rather than theoretical.

Common Misconception

A sprint review and a sprint retrospective are the same meeting.

What to Teach Instead

The sprint review examines the product -- what was built, whether it meets acceptance criteria, and what stakeholders think. The retrospective examines the process -- how the team worked together and what to improve next sprint. Both are valuable but serve different purposes. Conflating them causes teams to skip reflection on team dynamics, which Agile practitioners consider one of the most costly omissions.

Active Learning Ideas

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.

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

40 min·Small Groups

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.

25 min·Pairs

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.

30 min·Small Groups

Real-World Connections

• Software development teams at companies like Google and Microsoft use Scrum to manage the creation and updates of products such as Android and Windows, releasing new features in regular cycles.
• Game development studios, such as Blizzard Entertainment, employ Agile and Scrum to iterate on game mechanics and content, allowing for player feedback to influence development before release.
• Many tech startups utilize Scrum from their inception to quickly build and test Minimum Viable Products (MVPs), adapting their strategy based on early user testing and market response.

Assessment Ideas

Quick Check

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.

Discussion Prompt

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

Peer Assessment

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.

Frequently Asked Questions

What is the difference between Agile and Scrum?

Agile is a set of values and principles for software development, described in the Agile Manifesto published in 2001. Scrum is a specific framework that implements those principles through defined roles, ceremonies, and artifacts. Other Agile frameworks include Kanban, SAFe, and Extreme Programming. Scrum is the most widely used, particularly in product development teams at technology companies.

What happens during a sprint retrospective?

The retrospective is a structured team meeting at the end of each sprint where the team reflects on their working process -- not the product itself. Common formats ask what went well, what didn't, and what to try differently next sprint. The goal is continuous process improvement. Retrospectives are frequently skipped under time pressure, which is why experienced Agile coaches treat them as non-negotiable.

Why do so many companies use Agile instead of traditional Waterfall development?

Waterfall's major weakness is late problem discovery -- teams spend months building something only to find users don't actually want it. Agile's iterative cycles produce working software early, incorporate real feedback, and allow scope to evolve. Research on software project failures consistently identifies unclear requirements and late feedback as top causes, and Agile directly addresses both.

How does active learning help students understand Agile and Scrum frameworks?

Agile is best learned by doing. Running a real mini-sprint -- including planning, execution, review, and retrospective -- gives students direct experience with where the framework helps and where teams struggle. Classroom simulations surface coordination challenges that make abstract concepts like 'Definition of Done' immediately meaningful in a way that reading the Scrum Guide alone cannot.