Sean asks aquestion with anobvious answerthat leaves theroom speechlessORBcaused byOASIS-PSblack magicAn FDblames an“FC” insteadofthemselvesSomeonegetspaged3 or moretotallyundefinedacronyms usedon a singleslide“BadTechnicalInput”There’s aTDRS with one‘S’ and onewith two ‘S’s inthe same ORBSomeonementions a bestpracticesdocument thatno one knowsexistsSean saysORBs increaseat thebeginning ofthe semesterA CC makesa suggestthat getscompletelyshut downORB causedby ignoringcheckproductsoutputSomeonecomplainsabout nothavingenough coffeeORB causedbycompletelydisregardingprocedureAn ORBcaused byusing thewrong fileSomeonebrings upstudentprankingORB caused byonly one personknowing how toperform a taskAn ORBcaused by asimplesyntax errorPat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and ReidarORB causedby blindlyexecuting amanprocSean callspeople whoare glutenfree “special”ORB caused bymiscommunicationAn ORB withno actualeffect on thespacecraftSomeonepronouncesa CC’sname wrongMAVENishappyORBcaused byFC doinga CC taskAn ORBcaused bybad versioncontrolSomeonetalks about“the thoughtprocess”Funnyringtonegoes offSomeonefallsasleep3 or morespellingmistakes inone slideAn FDbrutallycriticizessomeoneSomeonesends anout of officeemailSean suggeststakingsomethingoffline that weall know won’tbeSomeoneassigns anaction itemto a studentAn ORBgoes fortwice as longas scheduledA CCITasks for asignature“PersonnelError”Impossibleaction itemsuggestedSean asks aquestion with anobvious answerthat leaves theroom speechlessORBcaused byOASIS-PSblack magicAn FDblames an“FC” insteadofthemselvesSomeonegetspaged3 or moretotallyundefinedacronyms usedon a singleslide“BadTechnicalInput”There’s aTDRS with one‘S’ and onewith two ‘S’s inthe same ORBSomeonementions a bestpracticesdocument thatno one knowsexistsSean saysORBs increaseat thebeginning ofthe semesterA CC makesa suggestthat getscompletelyshut downORB causedby ignoringcheckproductsoutputSomeonecomplainsabout nothavingenough coffeeORB causedbycompletelydisregardingprocedureAn ORBcaused byusing thewrong fileSomeonebrings upstudentprankingORB caused byonly one personknowing how toperform a taskAn ORBcaused by asimplesyntax errorPat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and ReidarORB causedby blindlyexecuting amanprocSean callspeople whoare glutenfree “special”ORB caused bymiscommunicationAn ORB withno actualeffect on thespacecraftSomeonepronouncesa CC’sname wrongMAVENishappyORBcaused byFC doinga CC taskAn ORBcaused bybad versioncontrolSomeonetalks about“the thoughtprocess”Funnyringtonegoes offSomeonefallsasleep3 or morespellingmistakes inone slideAn FDbrutallycriticizessomeoneSomeonesends anout of officeemailSean suggeststakingsomethingoffline that weall know won’tbeSomeoneassigns anaction itemto a studentAn ORBgoes fortwice as longas scheduledA CCITasks for asignature“PersonnelError”Impossibleaction 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. Sean asks a question with an obvious answer that leaves the room speechless
  2. ORB caused by OASIS-PS black magic
  3. An FD blames an “FC” instead of themselves
  4. Someone gets paged
  5. 3 or more totally undefined acronyms used on a single slide
  6. “Bad Technical Input”
  7. There’s a TDRS with one ‘S’ and one with two ‘S’s in the same ORB
  8. Someone mentions a best practices document that no one knows exists
  9. Sean says ORBs increase at the beginning of the semester
  10. A CC makes a suggest that gets completely shut down
  11. ORB caused by ignoring check products output
  12. Someone complains about not having enough coffee
  13. ORB caused by completely disregarding procedure
  14. An ORB caused by using the wrong file
  15. Someone brings up student pranking
  16. ORB caused by only one person knowing how to perform a task
  17. An ORB caused by a simple syntax error
  18. Pat starts talking about BDM and no one understands what he’s saying except for Gina and Robby and now Ross and Reidar
  19. ORB caused by blindly executing a manproc
  20. Sean calls people who are gluten free “special”
  21. ORB caused by miscommunication
  22. An ORB with no actual effect on the spacecraft
  23. Someone pronounces a CC’s name wrong
  24. MAVEN is happy
  25. ORB caused by FC doing a CC task
  26. An ORB caused by bad version control
  27. Someone talks about “the thought process”
  28. Funny ringtone goes off
  29. Someone falls asleep
  30. 3 or more spelling mistakes in one slide
  31. An FD brutally criticizes someone
  32. Someone sends an out of office email
  33. Sean suggests taking something offline that we all know won’t be
  34. Someone assigns an action item to a student
  35. An ORB goes for twice as long as scheduled
  36. A CCIT asks for a signature
  37. “Personnel Error”
  38. Impossible action item suggested