Impossibleaction itemsuggested,Sean callspeople whoare glutenfree“special”,“PersonnelError”,An ORBcaused by asimplesyntax error,An ORBgoes fortwice as longasscheduled,Funnyringtonegoes off,Someonebrings upstudentpranking,Someonepronouncesa CC’s namewrong,A CCITasks for asignature,An FDbrutallycriticizessomeone,ORB caused bymiscommunication,ORB caused byonly one personknowing how toperform a task,Someonefallsasleep,An ORB withno actualeffect on thespacecraft,ORB causedby ignoringcheckproductsoutput,Sean suggeststakingsomethingoffline that weall know won’tbe,Someonementions a bestpracticesdocument thatno one knowsexists,ORB causedby OASIS-PS blackmagic,An ORBcaused bybad versioncontrol,Someonetalks about“the thoughtprocess”,ORB causedby blindlyexecuting amanproc,A CC makesa suggestthat getscompletelyshut down,Sean asks aquestion with anobvious answerthat leaves theroom speechless,ORBcaused byFC doinga CC task,Someoneassigns anaction itemto a student,3 or morespellingmistakes inone slide,Someonesends anout of officeemail,MAVENishappy,Pat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and Reidar,ORB causedbycompletelydisregardingprocedure,3 or moretotallyundefinedacronyms usedon a singleslide,There’s a TDRSwith one ‘S’ andone with two‘S’s in the sameORB,“BadTechnicalInput”,An ORBcaused byusing thewrong file,Someonegetspaged,Sean saysORBs increaseat thebeginning ofthe semester,Someonecomplainsabout nothavingenough coffeeAn FDblames an“FC” insteadofthemselves,Impossibleaction itemsuggested,Sean callspeople whoare glutenfree“special”,“PersonnelError”,An ORBcaused by asimplesyntax error,An ORBgoes fortwice as longasscheduled,Funnyringtonegoes off,Someonebrings upstudentpranking,Someonepronouncesa CC’s namewrong,A CCITasks for asignature,An FDbrutallycriticizessomeone,ORB caused bymiscommunication,ORB caused byonly one personknowing how toperform a task,Someonefallsasleep,An ORB withno actualeffect on thespacecraft,ORB causedby ignoringcheckproductsoutput,Sean suggeststakingsomethingoffline that weall know won’tbe,Someonementions a bestpracticesdocument thatno one knowsexists,ORB causedby OASIS-PS blackmagic,An ORBcaused bybad versioncontrol,Someonetalks about“the thoughtprocess”,ORB causedby blindlyexecuting amanproc,A CC makesa suggestthat getscompletelyshut down,Sean asks aquestion with anobvious answerthat leaves theroom speechless,ORBcaused byFC doinga CC task,Someoneassigns anaction itemto a student,3 or morespellingmistakes inone slide,Someonesends anout of officeemail,MAVENishappy,Pat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and Reidar,ORB causedbycompletelydisregardingprocedure,3 or moretotallyundefinedacronyms usedon a singleslide,There’s a TDRSwith one ‘S’ andone with two‘S’s in the sameORB,“BadTechnicalInput”,An ORBcaused byusing thewrong file,Someonegetspaged,Sean saysORBs increaseat thebeginning ofthe semester,Someonecomplainsabout nothavingenough coffeeAn FDblames an“FC” insteadofthemselves,

ORB DAY BINGO - Call List

(Print) Use this randomly generated list as your call list when playing the game. There is no need to say the BINGO column name. Place some kind of mark (like an X, a checkmark, a dot, tally mark, etc) on each cell as you announce it, to keep track. You can also cut out each item, place them in a bag and pull words from the bag.


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
  1. Impossible action item suggested,
  2. Sean calls people who are gluten free “special”,
  3. “Personnel Error”,
  4. An ORB caused by a simple syntax error,
  5. An ORB goes for twice as long as scheduled,
  6. Funny ringtone goes off,
  7. Someone brings up student pranking,
  8. Someone pronounces a CC’s name wrong,
  9. A CCIT asks for a signature,
  10. An FD brutally criticizes someone,
  11. ORB caused by miscommunication,
  12. ORB caused by only one person knowing how to perform a task,
  13. Someone falls asleep,
  14. An ORB with no actual effect on the spacecraft,
  15. ORB caused by ignoring check products output,
  16. Sean suggests taking something offline that we all know won’t be,
  17. Someone mentions a best practices document that no one knows exists,
  18. ORB caused by OASIS-PS black magic,
  19. An ORB caused by bad version control,
  20. Someone talks about “the thought process”,
  21. ORB caused by blindly executing a manproc,
  22. A CC makes a suggest that gets completely shut down,
  23. Sean asks a question with an obvious answer that leaves the room speechless,
  24. ORB caused by FC doing a CC task,
  25. Someone assigns an action item to a student,
  26. 3 or more spelling mistakes in one slide,
  27. Someone sends an out of office email,
  28. MAVEN is happy,
  29. Pat starts talking about BDM and no one understands what he’s saying except for Gina and Robby and now Ross and Reidar,
  30. ORB caused by completely disregarding procedure,
  31. 3 or more totally undefined acronyms used on a single slide,
  32. There’s a TDRS with one ‘S’ and one with two ‘S’s in the same ORB,
  33. “Bad Technical Input”,
  34. An ORB caused by using the wrong file,
  35. Someone gets paged,
  36. Sean says ORBs increase at the beginning of the semester,
  37. Someone complains about not having enough coffee
  38. An FD blames an “FC” instead of themselves,