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

Managing Priorities in Sprints

Students will learn how teams manage conflicting priorities during a development sprint.

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

About This Topic

Managing priorities in a development sprint teaches students the practical realities of collaborative software work, where teams must navigate competing demands with limited time. Aligned with CSTA standards 3A-AP-19 and 3A-AP-22, this topic introduces students to agile-style sprint planning, a common practice in the US software industry.

In US K-12 computing, students often work on group programming projects without structured frameworks for dividing work or resolving disagreements. This topic gives students concrete tools: user stories, sprint backlogs, and explicit prioritization criteria. They learn to separate urgent from important, and to negotiate when team members have conflicting views on what to tackle first.

Active learning is particularly valuable here because sprint management is a social and decision-making skill as much as a technical one. Role-playing sprint planning meetings and critiquing team scenarios helps students build the interpersonal fluency that makes collaborative software development functional.

Key Questions

1. Explain how teams manage conflicting priorities during a development sprint.
2. Design a strategy for prioritizing tasks in a team project.
3. Critique different approaches to conflict resolution within a development team.

Learning Objectives

• Analyze a given sprint scenario to identify at least two conflicting priorities.
• Design a prioritization matrix for a set of user stories based on defined criteria.
• Evaluate the effectiveness of different conflict resolution strategies in a simulated sprint planning meeting.
• Explain the role of a product owner in managing sprint priorities.
• Critique a team's sprint backlog for clarity and feasibility.

Before You Start

Introduction to Agile Development

Why: Students need a basic understanding of agile principles and iterative development before learning about sprint management.

Team Collaboration and Communication

Why: Effective sprint management relies on clear communication and the ability to work cooperatively within a team.

Key Vocabulary

Sprint Backlog	A list of tasks identified by the team as needed to complete the work during a sprint. It is a forecast of the work to be done.
User Story	A short, simple description of a feature told from the perspective of the person who desires the new capability, usually a user or customer.
Prioritization Criteria	Specific factors used to rank tasks or user stories, such as business value, urgency, or effort required.
Scrum Master	A facilitator for the Scrum team who helps everyone understand Scrum theory, practices, rules, and values. They are responsible for removing impediments to the team's progress.
Product Owner	The person responsible for maximizing the value of the product resulting from the work of the Development Team. They manage the product backlog.

Watch Out for These Misconceptions

Common Misconception

The most technically interesting task should always be the top priority.

What to Teach Instead

Priority in a sprint is determined by user value, dependencies, and team capacity -- not by what is most technically interesting. Students often conflate personal interest with strategic importance. Sprint planning activities help them practice thinking from the user and project perspective first.

Common Misconception

A good team should never have conflicts over priorities.

What to Teach Instead

Conflicting priorities are normal in collaborative development because team members have different information, values, and constraints. The goal is not to eliminate conflict but to resolve it constructively using transparent criteria. Case study critiques help students develop conflict resolution vocabulary and strategies.

Common Misconception

Once a sprint starts, the team should never change its commitments.

What to Teach Instead

While sprint stability is important, significant new information (a critical bug, a changed requirement) can justify adjustments. The key is making changes deliberately and transparently rather than silently drifting. Students benefit from discussing the difference between scope creep and legitimate reprioritization.

Active Learning Ideas

Simulation Game: Sprint Planning Meeting

Groups of four receive a backlog of eight user stories with effort estimates and a two-week sprint time budget. Teams must select which stories to commit to, assign them, and justify their choices. A representative from each team explains their prioritization logic to the class.

35 min·Small Groups

Think-Pair-Share: Conflicting Priorities

Present a scenario where a team member insists on refactoring old code while others want to add a new feature before a deadline. Partners discuss how they would handle the conflict and what criteria they would use to decide. Pairs share their approaches and class identifies common principles.

20 min·Pairs

Task Triage Activity

Give groups a list of 12 potential tasks for a class project. Groups must categorize each as 'must do this sprint,' 'should do if time,' or 'defer to next sprint,' using a prioritization framework (e.g., urgency vs. impact matrix). Groups then compare their matrices and discuss why they classified items differently.

30 min·Small Groups

Case Study Critique: Team Conflict Scenarios

Students read short vignettes describing different team conflict situations (e.g., a developer who keeps changing scope mid-sprint, a team that never finishes anything because they keep reprioritizing). Individually students write a one-paragraph critique of the approach taken and a recommended alternative.

25 min·Individual

Real-World Connections

• Software development teams at companies like Google use agile methodologies, including sprints, to release new features for products such as Android and Chrome. They must constantly balance bug fixes with new feature development.
• Game development studios, such as Blizzard Entertainment, manage complex projects with many interdependent tasks. Prioritizing which in-game features or bug fixes to address in a development cycle is crucial for meeting release deadlines.
• Project managers in tech startups often use sprint-like cycles to iterate on product development, responding quickly to user feedback and market demands. They must make tough decisions about what features to build next with limited resources.

Assessment Ideas

Exit Ticket

Provide students with a short scenario describing a team facing a time crunch with multiple urgent requests. Ask them to list two potential conflicting priorities and one strategy they would suggest to resolve them.

Discussion Prompt

Present students with two different methods for prioritizing tasks: one based solely on urgency, and another balancing urgency with estimated effort. Ask: 'Which method is more likely to lead to a successful sprint, and why? Consider potential drawbacks of each.'

Quick Check

Give students a list of 5 user stories for a hypothetical app. Instruct them to rank these stories from highest to lowest priority, providing a one-sentence justification for their top-ranked choice based on a given business goal.

Frequently Asked Questions

How do development teams prioritize tasks during a sprint?

Teams typically use a combination of user impact, technical dependencies, effort estimates, and deadlines to sequence tasks. Frameworks like MoSCoW (Must have, Should have, Could have, Won't have) or urgency-impact matrices help make prioritization criteria explicit and discussable rather than based on whoever argues loudest.

How do you handle conflicting priorities in a student software team?

Establish shared prioritization criteria before disagreements arise, so decisions are made against agreed standards rather than personal preferences. When conflicts occur, surface the different assumptions each person is making -- often the disagreement is about facts or constraints, not values, and can be resolved with more information.

What is a sprint in agile software development?

A sprint is a fixed-length development cycle, typically one to four weeks, during which a team commits to completing a defined set of tasks from a prioritized backlog. At the end of the sprint, the team reviews what was completed, reflects on the process, and plans the next sprint.

How does active learning help students practice sprint management?

Sprint management requires negotiation, judgment under time pressure, and team communication -- skills that cannot be developed passively. Simulated planning meetings and task triage exercises put students in realistic decision-making situations where they must practice these skills rather than just read about them.