Agile and Scrum software development are the focus of this Grade 11 Computer Science worksheet for Software Engineering. Students compare iterative agile planning with more traditional sequential development while learning how Scrum uses sprints, feedback, roles, ceremonies, and a changing product backlog to respond to new requirements. :contentReference[oaicite:0]{index=0}

See how teams respond when requirements change

The resource emphasizes one of the central ideas behind agile development: teams expect change and organize work so they can adjust sooner. Students examine how smaller iterations allow teams to deliver working pieces of software, review progress, gather feedback, and revise priorities instead of waiting until the end of a long development process.

Scrum provides the practical framework for this comparison. Students work with sprints as time-boxed periods of development, the Daily Scrum as a way to coordinate work and address obstacles, and the Sprint Review as an opportunity to demonstrate an increment and collect stakeholder feedback. They also examine the Scrum Master, Developers, Sprint Planning, sprint goals, and the product backlog. :contentReference[oaicite:1]{index=1}

Practice connects Scrum concepts with project decisions

• A dialogue-based question introduces agile responses to changing requirements
• Matching practice connects Scrum terminology with its purpose
• A cloze passage reinforces iterations, sprints, daily meetings, reviews, backlog items, and priorities
• A diagram-labeling activity supports visual understanding of the Scrum workflow
• An informational reading passage compares iterative planning with longer sequential development
• Multiple-choice questions apply sprints, reviews, roles, backlog updates, and feedback to realistic situations
• True-or-false statements check understanding of Sprint Planning, Daily Scrum, Sprint Reviews, and changing priorities
• Short-answer questions ask students to explain feedback, daily coordination, and requirement changes
• An extended response requires students to explain how Scrum would respond to a late change in user needs

Connect feedback to the next development cycle

The extended scenario asks students to consider a team that discovers late in development that users need a different login method. Students explain how an agile Scrum team could use roles, sprints, check-ins, sprint review feedback, and the product backlog to manage that change across multiple cycles. This helps students connect individual Scrum terms into a complete response-to-change process.

The worksheet can be used for guided Software Engineering practice, independent work, homework, review, or conceptual assessment. A separate Teacher Guide PDF includes learning objectives, teaching tips, discussion questions, and common mistakes to support lesson preparation and classroom discussion.