ORBcaused byFC doinga CC taskAn FDbrutallycriticizessomeoneORB causedby blindlyexecuting amanprocAn ORB withno actualeffect on thespacecraftORB caused byonly one personknowing how toperform a taskSomeonecomplainsabout nothavingenough coffeeORB causedby ignoringcheckproductsoutputSomeonepronouncesa CC’sname wrongMAVENishappyAn ORBcaused byusing thewrong filePat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and ReidarAn ORBcaused by asimplesyntax errorA CC makesa suggestthat getscompletelyshut downThere’s aTDRS with one‘S’ and onewith two ‘S’s inthe same ORBSomeonementions a bestpracticesdocument thatno one knowsexistsORB causedbycompletelydisregardingprocedureSean asks aquestion with anobvious answerthat leaves theroom speechless3 or moretotallyundefinedacronyms usedon a singleslideSomeonegetspagedORBcaused byOASIS-PSblack magicFunnyringtonegoes offSean saysORBs increaseat thebeginning ofthe semesterSomeoneassigns anaction itemto a studentAn ORBcaused bybad versioncontrolA CCITasks for asignature“PersonnelError”Impossibleaction itemsuggestedSomeonefallsasleepSomeonetalks about“the thoughtprocess”“BadTechnicalInput”An FDblames an“FC” insteadofthemselvesSomeonebrings upstudentpranking3 or morespellingmistakes inone slideAn ORBgoes fortwice as longas scheduledSean suggeststakingsomethingoffline that weall know won’tbeSean callspeople whoare glutenfree “special”Someonesends anout of officeemailORB caused bymiscommunicationORBcaused byFC doinga CC taskAn FDbrutallycriticizessomeoneORB causedby blindlyexecuting amanprocAn ORB withno actualeffect on thespacecraftORB caused byonly one personknowing how toperform a taskSomeonecomplainsabout nothavingenough coffeeORB causedby ignoringcheckproductsoutputSomeonepronouncesa CC’sname wrongMAVENishappyAn ORBcaused byusing thewrong filePat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and ReidarAn ORBcaused by asimplesyntax errorA CC makesa suggestthat getscompletelyshut downThere’s aTDRS with one‘S’ and onewith two ‘S’s inthe same ORBSomeonementions a bestpracticesdocument thatno one knowsexistsORB causedbycompletelydisregardingprocedureSean asks aquestion with anobvious answerthat leaves theroom speechless3 or moretotallyundefinedacronyms usedon a singleslideSomeonegetspagedORBcaused byOASIS-PSblack magicFunnyringtonegoes offSean saysORBs increaseat thebeginning ofthe semesterSomeoneassigns anaction itemto a studentAn ORBcaused bybad versioncontrolA CCITasks for asignature“PersonnelError”Impossibleaction itemsuggestedSomeonefallsasleepSomeonetalks about“the thoughtprocess”“BadTechnicalInput”An FDblames an“FC” insteadofthemselvesSomeonebrings upstudentpranking3 or morespellingmistakes inone slideAn ORBgoes fortwice as longas scheduledSean suggeststakingsomethingoffline that weall know won’tbeSean callspeople whoare glutenfree “special”Someonesends anout of officeemailORB caused bymiscommunication

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