An ORBgoes fortwice as longas scheduledThere’s aTDRS with one‘S’ and onewith two ‘S’s inthe same ORBORB caused byonly one personknowing how toperform a taskPat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and ReidarSean asks aquestion with anobvious answerthat leaves theroom speechlessORBcaused byOASIS-PSblack magicMAVENishappyAn FDbrutallycriticizessomeoneA CC makesa suggestthat getscompletelyshut down3 or morespellingmistakes inone slideAn ORB withno actualeffect on thespacecraft“BadTechnicalInput”Someonetalks about“the thoughtprocess”SomeonefallsasleepAn FDblames an“FC” insteadofthemselvesSomeonebrings upstudentprankingAn ORBcaused bybad versioncontrolSomeonepronouncesa CC’sname wrongORB causedby blindlyexecuting amanprocORB caused bymiscommunicationSomeonementions a bestpracticesdocument thatno one knowsexistsFunnyringtonegoes offORB causedbycompletelydisregardingprocedureSean saysORBs increaseat thebeginning ofthe semesterORBcaused byFC doinga CC taskSomeonecomplainsabout nothavingenough coffeeAn ORBcaused byusing thewrong file3 or moretotallyundefinedacronyms usedon a singleslideSean suggeststakingsomethingoffline that weall know won’tbeSomeonesends anout of officeemailA CCITasks for asignatureSean callspeople whoare glutenfree “special”ORB causedby ignoringcheckproductsoutputSomeoneassigns anaction itemto a studentSomeonegetspagedImpossibleaction itemsuggested“PersonnelError”An ORBcaused by asimplesyntax errorAn ORBgoes fortwice as longas scheduledThere’s aTDRS with one‘S’ and onewith two ‘S’s inthe same ORBORB caused byonly one personknowing how toperform a taskPat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and ReidarSean asks aquestion with anobvious answerthat leaves theroom speechlessORBcaused byOASIS-PSblack magicMAVENishappyAn FDbrutallycriticizessomeoneA CC makesa suggestthat getscompletelyshut down3 or morespellingmistakes inone slideAn ORB withno actualeffect on thespacecraft“BadTechnicalInput”Someonetalks about“the thoughtprocess”SomeonefallsasleepAn FDblames an“FC” insteadofthemselvesSomeonebrings upstudentprankingAn ORBcaused bybad versioncontrolSomeonepronouncesa CC’sname wrongORB causedby blindlyexecuting amanprocORB caused bymiscommunicationSomeonementions a bestpracticesdocument thatno one knowsexistsFunnyringtonegoes offORB causedbycompletelydisregardingprocedureSean saysORBs increaseat thebeginning ofthe semesterORBcaused byFC doinga CC taskSomeonecomplainsabout nothavingenough coffeeAn ORBcaused byusing thewrong file3 or moretotallyundefinedacronyms usedon a singleslideSean suggeststakingsomethingoffline that weall know won’tbeSomeonesends anout of officeemailA CCITasks for asignatureSean callspeople whoare glutenfree “special”ORB causedby ignoringcheckproductsoutputSomeoneassigns anaction itemto a studentSomeonegetspagedImpossibleaction itemsuggested“PersonnelError”An ORBcaused by asimplesyntax error

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