A CC makesa suggestthat getscompletelyshut down“PersonnelError”Sean asks aquestion with anobvious answerthat leaves theroom speechlessORBcaused byOASIS-PSblack magicAn FDbrutallycriticizessomeone3 or moretotallyundefinedacronyms usedon a singleslideORB caused bymiscommunicationAn ORBcaused bybad versioncontrolSomeonetalks about“the thoughtprocess”SomeonefallsasleepORB causedby blindlyexecuting amanprocSean saysORBs increaseat thebeginning ofthe semesterAn ORB withno actualeffect on thespacecraftSomeonementions a bestpracticesdocument thatno one knowsexistsAn ORBcaused by asimplesyntax errorSomeonebrings upstudentprankingPat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and ReidarORB causedby ignoringcheckproductsoutput“BadTechnicalInput”A CCITasks for asignatureSomeoneassigns anaction itemto a studentSomeonesends anout of officeemailMAVENishappyImpossibleaction itemsuggestedSean callspeople whoare glutenfree “special”SomeonegetspagedSomeonecomplainsabout nothavingenough coffeeORB causedbycompletelydisregardingprocedureORBcaused byFC doinga CC taskAn FDblames an“FC” insteadofthemselvesORB caused byonly one personknowing how toperform a taskAn ORBcaused byusing thewrong fileSomeonepronouncesa CC’sname wrongThere’s aTDRS with one‘S’ and onewith two ‘S’s inthe same ORB3 or morespellingmistakes inone slideFunnyringtonegoes offAn ORBgoes fortwice as longas scheduledSean suggeststakingsomethingoffline that weall know won’tbeA CC makesa suggestthat getscompletelyshut down“PersonnelError”Sean asks aquestion with anobvious answerthat leaves theroom speechlessORBcaused byOASIS-PSblack magicAn FDbrutallycriticizessomeone3 or moretotallyundefinedacronyms usedon a singleslideORB caused bymiscommunicationAn ORBcaused bybad versioncontrolSomeonetalks about“the thoughtprocess”SomeonefallsasleepORB causedby blindlyexecuting amanprocSean saysORBs increaseat thebeginning ofthe semesterAn ORB withno actualeffect on thespacecraftSomeonementions a bestpracticesdocument thatno one knowsexistsAn ORBcaused by asimplesyntax errorSomeonebrings upstudentprankingPat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and ReidarORB causedby ignoringcheckproductsoutput“BadTechnicalInput”A CCITasks for asignatureSomeoneassigns anaction itemto a studentSomeonesends anout of officeemailMAVENishappyImpossibleaction itemsuggestedSean callspeople whoare glutenfree “special”SomeonegetspagedSomeonecomplainsabout nothavingenough coffeeORB causedbycompletelydisregardingprocedureORBcaused byFC doinga CC taskAn FDblames an“FC” insteadofthemselvesORB caused byonly one personknowing how toperform a taskAn ORBcaused byusing thewrong fileSomeonepronouncesa CC’sname wrongThere’s aTDRS with one‘S’ and onewith two ‘S’s inthe same ORB3 or morespellingmistakes inone slideFunnyringtonegoes offAn ORBgoes fortwice as longas scheduledSean suggeststakingsomethingoffline that weall know won’tbe

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