Computer Science · 12th Grade

Active learning ideas

Software Engineering Capstone: Project Planning

Active learning works for project planning because students must experience the tension between idealized plans and real-world constraints. When they practice gathering requirements from a mock client or defend scope decisions in a group, they confront the messy gaps between user needs and technical execution.

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

• 30–75 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Project-Based Learning
• 40 min · Pairs

Role-Play: Client Requirements Interview

Pairs take turns playing 'client' and 'developer.' The client has a brief describing a vague software need; the developer must ask targeted questions to extract specific, testable requirements. After 15 minutes, pairs swap roles with a different scenario. Debrief focuses on which questions surfaced the most useful information and which assumptions developers nearly baked in without asking.

Design a comprehensive project plan, including scope, timeline, and resource allocation.

Facilitation Tip

During the Role-Play: Client Requirements Interview, circulate with a clipboard to note which students ask clarifying questions versus those who jump to solutions.

What to look for

Provide students with a brief description of a hypothetical software project (e.g., a mobile app for local event discovery). Ask them to write down: 1) Two specific user stories for the app, and 2) One potential challenge in translating user needs into technical requirements for this app.

• Apply
• Analyze
• Evaluate
• Create
• Self-Management
• Relationship Skills
• Decision-Making

Activity 02

• Think-Pair-Share
• 30 min · Pairs

Think-Pair-Share: Scope Definition Challenge

Present a project brief with an intentionally broad scope (e.g., 'build an app for the school library'). Individually, students list 10 features they assume the project includes. Pairs compare lists , the divergence illustrates why explicit scope documents matter. Each pair then drafts a one-paragraph scope statement that would resolve the ambiguities they identified.

Analyze the challenges of translating user needs into technical requirements.

Facilitation Tip

In the Think-Pair-Share: Scope Definition Challenge, stop the pair discussion after two minutes to call on groups that disagree on feature prioritization.

What to look for

Present students with a sample project scope document that contains vague language or missing key sections. Ask them to identify at least two areas that need clarification or expansion, explaining why they are problematic for project planning.

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

Activity 03

• Gallery Walk
• 45 min · Small Groups

Gallery Walk: Development Methodology Trade-offs

Post stations describing Waterfall, Agile (Scrum), Kanban, and Spiral methodologies with a project scenario attached to each. Student groups rotate and annotate each station: what are the advantages and risks of this methodology for this project? The debrief surfaces the insight that methodology choice depends on project context, not on which is 'best' in the abstract.

Justify the choice of development methodologies for a given project.

Facilitation Tip

For the Gallery Walk: Development Methodology Trade-offs, post a large matrix on the wall where students physically place sticky notes to mark their preferred methodology for each scenario.

What to look for

Facilitate a class discussion using the prompt: 'Imagine you are leading a capstone project and have two potential clients with slightly conflicting needs. How would you use requirements gathering techniques and scope definition to manage these expectations and create a unified project plan?'

• Understand
• Apply
• Analyze
• Create
• Relationship Skills
• Social Awareness

Activity 04

• Project-Based Learning
• 75 min · Individual

Design Workshop: Full Project Plan Draft

Each student drafts an initial project plan for their capstone: a scope statement, a list of functional and non-functional requirements, a preliminary timeline with milestones, and a justification of their chosen methodology. Peer reviewers use a structured checklist to identify gaps in requirements specificity and timeline realism before the plan is submitted.

Design a comprehensive project plan, including scope, timeline, and resource allocation.

Facilitation Tip

In the Design Workshop: Full Project Plan Draft, require each group to present their project plan to another group before submitting it for peer review.

What to look for

Provide students with a brief description of a hypothetical software project (e.g., a mobile app for local event discovery). Ask them to write down: 1) Two specific user stories for the app, and 2) One potential challenge in translating user needs into technical requirements for this app.

• Apply
• Analyze
• Evaluate
• Create
• Self-Management
• Relationship Skills
• Decision-Making

A few notes on teaching this unit

Teachers should treat this topic as a cycle of negotiation, not a linear process. Research shows that students grasp project planning best when they repeatedly revise artifacts under time pressure, so avoid letting groups finalize documents too early. Emphasize that the goal is not perfection but disciplined iteration, where students learn to surface assumptions and adjust based on feedback.

Successful learning looks like students shifting from vague ideas to concrete artifacts with measurable constraints. They should begin articulating user needs as testable requirements, defining scope with explicit trade-offs, and aligning their design choices with methodology trade-offs.

---

Watch Out for These Misconceptions

• During Role-Play: Client Requirements Interview, some students may assume the client’s first answer is the final requirement.

  After the role-play ends, have students revisit their notes and circle any requirements that are vague or tied to assumptions. They must draft follow-up questions to refine those requirements before moving to the next activity.

• During Think-Pair-Share: Scope Definition Challenge, students may believe adding more features always improves the project.

  Use the group’s shared document to highlight where features conflict with the time box. Ask each pair to defend their top three features against the project timeline, then remove one feature if it exceeds the scope.

• During Gallery Walk: Development Methodology Trade-offs, students might think Agile is always superior to Waterfall.

  Provide a scenario with high regulatory constraints (e.g., medical software) and ask students to justify why a hybrid approach might work better. They must present their reasoning to the class during the gallery walk.

---

Methods used in this brief

• Project-Based Learning
• Think-Pair-Share
• Gallery Walk