Someonebrings upstudentprankingSean suggeststakingsomethingoffline that weall know won’tbeAn ORBcaused bybad versioncontrolORB caused bymiscommunicationSomeonementions a bestpracticesdocument thatno one knowsexistsORBcaused byFC doinga CC taskA CCITasks for asignatureFunnyringtonegoes offSomeonegetspagedORB causedby blindlyexecuting amanprocPat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and ReidarMAVENishappySean saysORBs increaseat thebeginning ofthe semesterSean callspeople whoare glutenfree “special”Someonetalks about“the thoughtprocess”Someonesends anout of officeemailAn ORBgoes fortwice as longas scheduled“PersonnelError”ORB causedbycompletelydisregardingprocedureImpossibleaction itemsuggestedSomeonecomplainsabout nothavingenough coffeeAn ORBcaused byusing thewrong fileSomeonefallsasleep3 or moretotallyundefinedacronyms usedon a singleslideSean asks aquestion with anobvious answerthat leaves theroom speechlessAn ORB withno actualeffect on thespacecraftORB causedby ignoringcheckproductsoutputAn FDbrutallycriticizessomeoneAn ORBcaused by asimplesyntax error3 or morespellingmistakes inone slideThere’s aTDRS with one‘S’ and onewith two ‘S’s inthe same ORBSomeoneassigns anaction itemto a studentORB caused byonly one personknowing how toperform a task“BadTechnicalInput”ORBcaused byOASIS-PSblack magicA CC makesa suggestthat getscompletelyshut downSomeonepronouncesa CC’sname wrongAn FDblames an“FC” insteadofthemselvesSomeonebrings upstudentprankingSean suggeststakingsomethingoffline that weall know won’tbeAn ORBcaused bybad versioncontrolORB caused bymiscommunicationSomeonementions a bestpracticesdocument thatno one knowsexistsORBcaused byFC doinga CC taskA CCITasks for asignatureFunnyringtonegoes offSomeonegetspagedORB causedby blindlyexecuting amanprocPat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and ReidarMAVENishappySean saysORBs increaseat thebeginning ofthe semesterSean callspeople whoare glutenfree “special”Someonetalks about“the thoughtprocess”Someonesends anout of officeemailAn ORBgoes fortwice as longas scheduled“PersonnelError”ORB causedbycompletelydisregardingprocedureImpossibleaction itemsuggestedSomeonecomplainsabout nothavingenough coffeeAn ORBcaused byusing thewrong fileSomeonefallsasleep3 or moretotallyundefinedacronyms usedon a singleslideSean asks aquestion with anobvious answerthat leaves theroom speechlessAn ORB withno actualeffect on thespacecraftORB causedby ignoringcheckproductsoutputAn FDbrutallycriticizessomeoneAn ORBcaused by asimplesyntax error3 or morespellingmistakes inone slideThere’s aTDRS with one‘S’ and onewith two ‘S’s inthe same ORBSomeoneassigns anaction itemto a studentORB caused byonly one personknowing how toperform a task“BadTechnicalInput”ORBcaused byOASIS-PSblack magicA CC makesa suggestthat getscompletelyshut downSomeonepronouncesa CC’sname wrongAn FDblames an“FC” insteadofthemselves

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