Follow this in order. Blue = say out loud. Amber = action to take. Red = watch for this.
0
Before Class -- Setup
5 min before
✓ Open this dashboard on YOUR device (laptop/tablet projected or in hand).
✓ Write the 6 team links on the board or paste them in the class chat:
Board / Chat
Replace YOUR-SITE-HERE with your actual GitHub Pages URL.
✓ Confirm all 6 team links are visible before students arrive.
✓ Decide how to divide 45 students into 6 groups (7-8 per group).
✓ Only ONE device per team opens the team link -- the others watch or discuss.
1
Introduce the Game
~2 min
Say this
"Today we're doing a 20-minute mission simulation called Operation Bagyo. You're a project management team at PhilSpace -- the Philippine space agency. Each team has a different satellite mission to plan. You'll complete four rounds covering the concepts from Chapters 4 and 5."
Say this
"Each team: one person opens your team's link on your phone or laptop. That person controls the screen -- but everyone in the group should discuss the answers together. If you haven't read the chapter, don't worry -- each round starts with a short lesson."
Do this
Announce team assignments. Give teams 1-2 minutes to open their link and read their scenario.
2
Round 1 -- Project Charter + Priority + Feasibility
~6 min
Say this
"Click 'Read Lesson' on your screen first -- it explains what a Project Charter is. Then click 'Start Round 1' to begin. You'll fill out three sections: the Charter (WHAT, WHEN, HOW MUCH), the Priority Matrix (which constraint is fixed vs. flexible), and a Feasibility check."
Do this
Click "Start Timer" on this dashboard now. Teams have 6 minutes for Round 1.
Watch for this
Priority Matrix confusion: Some teams mark the same letter (e.g. two C's) in the matrix. The app warns them, but you can remind them: "Each row gets a different letter -- one C, one A, one E."
Watch for this
Charter fields left blank: Each field (WHAT/WHEN/HOW MUCH) is worth 1 point. Remind teams not to skip any.
Teaching Tip
The Priority Matrix answer depends on each team's scenario. Each scenario has a different constrained variable -- that's intentional. When debriefing, ask each team to explain WHY their scenario led to that priority choice.
3
Round 2A -- Work Breakdown Structure
~5 min
Say this
"Round 2 has two parts. First: the WBS sort. You'll see 12 work packages. Your job is to mark each one as VALID (it belongs in the satellite project) or DISCARD (it doesn't belong). Read the mini lesson first if you're unsure."
Do this
Tell teams to click "Next: WBS Sort" when they finish Round 1. They'll see the lesson first, then Round 2A.
Watch for this
Red herring tiles: The four red herrings -- Team Lunch Budget, Morale and Wellness Program, Office Renovation, Social Media Campaign -- are NOT project deliverables. Teams that keep all four lose points. If you see a team struggling, you can hint: "Does office renovation belong in a satellite project scope?"
Teaching Tip
After the game, ask: "How did you decide what to discard?" Good answers mention: the work package is not a deliverable of the satellite mission; it's a support or admin activity; or it doesn't appear in the project's scope statement.
4
Round 2B -- Cost Estimation and Budget
~4 min
Say this
"Now estimate the cost for each work package you marked as VALID. Each tile has a range -- pick a number within that range. Your total budget should land between PHP 1,900M and 2,200M to earn full points."
Do this
Tell teams to click "Next: Budget" on their screen. The budget table shows only the tiles they marked as VALID.
Watch for this
Budget too high: If teams kept all 12 tiles (including red herrings), their budget will be way over PHP 2,200M -- this is intentional. It teaches them that scope must be controlled. Don't correct them yet; let the score reflect it.
Watch for this
Budget not submitted: Remind teams to click "Submit Budget" once they've entered all their cost estimates.
Teaching Tip
The optimal range (PHP 1,900M - 2,200M) is the sum of the midpoints of the 8 valid tile ranges. This rewards teams who picked realistic middle estimates rather than always the minimum or maximum.
5
Round 3 -- Project Change / Anomaly
~3 min
Say this
"An unexpected situation has come up on your mission. Read the anomaly card carefully. You must choose: ACCEPT the change, NEGOTIATE a different solution, or REJECT it. Then write a one-sentence justification."
Do this
Tell teams to click "Next: Anomaly" on their screen.
Watch for this
Justification left blank or too vague: The justification is worth up to 4 points. To earn full marks, teams must: (1) choose NEGOTIATE, (2) mention the specific PHP amount from their anomaly options, and (3) name which constraint is most affected (Cost, Time, or Scope). Remind them if time allows.
Teaching Tip
Each team has a different anomaly card, so their "correct" answer differs slightly. But NEGOTIATE is almost always best. Ask teams during debrief: "Why not just ACCEPT? Why not REJECT?" Good PM students understand that rejection ignores reality and blind acceptance gives up negotiating power.
6
Reveal Scores and Debrief
~5 min
Do this
Click "Show Final Scores" below, then switch to the Live Scores tab to display the leaderboard. You can also share the WBS Answer Key, Priority Answers, and Anomaly Answers tabs to walk through each section.
Debrief questions
"Which part was hardest? Why did you discard (or keep) the red herring tiles? What did your Priority Matrix say about your mission constraints? If you could redo the anomaly response, what would you change?"
Teaching Tip
Connect each round to the textbook: Round 1 = Chapter 4 (Project Charter and Scope Statement). Round 2 = Chapter 5 (WBS and Cost Estimation). Round 3 = Chapter 7 (Risk and Change Management). Ask students: "Where did you see the textbook concepts in action just now?"
Quick Scoring Reference (Max 21 Points)
Round 1A -- Charter (3 pts)
1 pt -- WHAT field filled in
1 pt -- WHEN field filled in
1 pt -- HOW MUCH field filled in
Round 1B -- Priority Matrix (2 pts)
1 pt -- All 3 rows marked (C/A/E)
1 pt -- Matches the correct answer for their scenario
Round 1C -- Feasibility (2 pts)
1 pt -- 2 or more boxes checked
1 pt -- Choices are consistent with their scenario constraints
Scores update when teams submit their final answers. If a team's score is not showing, ask them to click "Submit" on their anomaly screen.
WBS Answer Key -- All 12 Tiles
#
Work Package
Cost Range
Verdict
Level
Why
💡
Teaching point: Level 1 = Major Deliverables (the big outputs -- what the project produces). Level 2 = Work Packages (specific tasks that contribute to a Level 1 deliverable). Red Herrings are not project deliverables at all -- they belong outside the satellite mission's scope.
Priority Matrix Answers by Scenario
💡
Teaching point: Only ONE variable should be Enhanced (push to improve), ONE Constrained (fixed, cannot change), and ONE Accepted (flexible, can slip). The three markers must all be different -- no scenario should have two C's or two E's.
Anomaly Answer Key by Team
💡
Teaching point: NEGOTIATE is almost always the best answer in project management because it acknowledges the problem while minimizing damage. REJECT (doing nothing) is usually the worst. Ask teams to justify using the specific PHP amounts and which constraint is affected -- that's where real project thinking happens.