ORB caused bymiscommunicationSean saysORBs increaseat thebeginning ofthe semesterORBcaused byFC doinga CC taskSomeonesends anout of officeemailAn ORBcaused bybad versioncontrolSomeonepronouncesa CC’sname wrongORB causedby ignoringcheckproductsoutputA CCITasks for asignatureSomeonegetspagedSean callspeople whoare glutenfree “special”Sean asks aquestion with anobvious answerthat leaves theroom speechlessORB causedby blindlyexecuting amanprocMAVENishappyAn ORBgoes fortwice as longas scheduledA CC makesa suggestthat getscompletelyshut downSomeonebrings upstudentprankingAn FDblames an“FC” insteadofthemselves3 or morespellingmistakes inone slideSean suggeststakingsomethingoffline that weall know won’tbeThere’s aTDRS with one‘S’ and onewith two ‘S’s inthe same ORB3 or moretotallyundefinedacronyms usedon a singleslideSomeonementions a bestpracticesdocument thatno one knowsexistsImpossibleaction itemsuggestedORB causedbycompletelydisregardingprocedureFunnyringtonegoes offSomeoneassigns anaction itemto a studentAn ORB withno actualeffect on thespacecraftPat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and ReidarORB caused byonly one personknowing how toperform a taskSomeonetalks about“the thoughtprocess”“PersonnelError”SomeonefallsasleepSomeonecomplainsabout nothavingenough coffee“BadTechnicalInput”ORBcaused byOASIS-PSblack magicAn ORBcaused by asimplesyntax errorAn FDbrutallycriticizessomeoneAn ORBcaused byusing thewrong fileORB caused bymiscommunicationSean saysORBs increaseat thebeginning ofthe semesterORBcaused byFC doinga CC taskSomeonesends anout of officeemailAn ORBcaused bybad versioncontrolSomeonepronouncesa CC’sname wrongORB causedby ignoringcheckproductsoutputA CCITasks for asignatureSomeonegetspagedSean callspeople whoare glutenfree “special”Sean asks aquestion with anobvious answerthat leaves theroom speechlessORB causedby blindlyexecuting amanprocMAVENishappyAn ORBgoes fortwice as longas scheduledA CC makesa suggestthat getscompletelyshut downSomeonebrings upstudentprankingAn FDblames an“FC” insteadofthemselves3 or morespellingmistakes inone slideSean suggeststakingsomethingoffline that weall know won’tbeThere’s aTDRS with one‘S’ and onewith two ‘S’s inthe same ORB3 or moretotallyundefinedacronyms usedon a singleslideSomeonementions a bestpracticesdocument thatno one knowsexistsImpossibleaction itemsuggestedORB causedbycompletelydisregardingprocedureFunnyringtonegoes offSomeoneassigns anaction itemto a studentAn ORB withno actualeffect on thespacecraftPat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and ReidarORB caused byonly one personknowing how toperform a taskSomeonetalks about“the thoughtprocess”“PersonnelError”SomeonefallsasleepSomeonecomplainsabout nothavingenough coffee“BadTechnicalInput”ORBcaused byOASIS-PSblack magicAn ORBcaused by asimplesyntax errorAn FDbrutallycriticizessomeoneAn ORBcaused byusing thewrong file

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