3 or moretotallyundefinedacronyms usedon a singleslideAn FDbrutallycriticizessomeone“PersonnelError”An ORBcaused by asimplesyntax errorSean saysORBs increaseat thebeginning ofthe semesterORB caused bymiscommunicationSomeonesends anout of officeemailAn ORBcaused byusing thewrong fileSean callspeople whoare glutenfree “special”Sean suggeststakingsomethingoffline that weall know won’tbeORBcaused byOASIS-PSblack magicThere’s aTDRS with one‘S’ and onewith two ‘S’s inthe same ORBORB causedby blindlyexecuting amanprocSomeonementions a bestpracticesdocument thatno one knowsexistsSean asks aquestion with anobvious answerthat leaves theroom speechless3 or morespellingmistakes inone slideSomeonetalks about“the thoughtprocess”Someonebrings upstudentprankingA CC makesa suggestthat getscompletelyshut downSomeonegetspaged“BadTechnicalInput”A CCITasks for asignatureSomeonepronouncesa CC’sname wrongPat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and ReidarAn ORBcaused bybad versioncontrolAn FDblames an“FC” insteadofthemselvesMAVENishappyORB caused byonly one personknowing how toperform a taskAn ORBgoes fortwice as longas scheduledORB causedby ignoringcheckproductsoutputORB causedbycompletelydisregardingprocedureSomeonecomplainsabout nothavingenough coffeeORBcaused byFC doinga CC taskSomeonefallsasleepSomeoneassigns anaction itemto a studentFunnyringtonegoes offAn ORB withno actualeffect on thespacecraftImpossibleaction itemsuggested3 or moretotallyundefinedacronyms usedon a singleslideAn FDbrutallycriticizessomeone“PersonnelError”An ORBcaused by asimplesyntax errorSean saysORBs increaseat thebeginning ofthe semesterORB caused bymiscommunicationSomeonesends anout of officeemailAn ORBcaused byusing thewrong fileSean callspeople whoare glutenfree “special”Sean suggeststakingsomethingoffline that weall know won’tbeORBcaused byOASIS-PSblack magicThere’s aTDRS with one‘S’ and onewith two ‘S’s inthe same ORBORB causedby blindlyexecuting amanprocSomeonementions a bestpracticesdocument thatno one knowsexistsSean asks aquestion with anobvious answerthat leaves theroom speechless3 or morespellingmistakes inone slideSomeonetalks about“the thoughtprocess”Someonebrings upstudentprankingA CC makesa suggestthat getscompletelyshut downSomeonegetspaged“BadTechnicalInput”A CCITasks for asignatureSomeonepronouncesa CC’sname wrongPat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and ReidarAn ORBcaused bybad versioncontrolAn FDblames an“FC” insteadofthemselvesMAVENishappyORB caused byonly one personknowing how toperform a taskAn ORBgoes fortwice as longas scheduledORB causedby ignoringcheckproductsoutputORB causedbycompletelydisregardingprocedureSomeonecomplainsabout nothavingenough coffeeORBcaused byFC doinga CC taskSomeonefallsasleepSomeoneassigns anaction itemto a studentFunnyringtonegoes offAn ORB withno actualeffect on thespacecraftImpossibleaction itemsuggested

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