Pat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and ReidarAn FDblames an“FC” insteadofthemselvesSomeonefallsasleepORB causedby ignoringcheckproductsoutputSomeonesends anout of officeemailORB caused byonly one personknowing how toperform a taskSean saysORBs increaseat thebeginning ofthe semester3 or morespellingmistakes inone slideORBcaused byOASIS-PSblack magicSomeonepronouncesa CC’sname wrongSean asks aquestion with anobvious answerthat leaves theroom speechlessSomeoneassigns anaction itemto a studentORB caused bymiscommunication“PersonnelError”There’s aTDRS with one‘S’ and onewith two ‘S’s inthe same ORBSomeonetalks about“the thoughtprocess”An ORBcaused bybad versioncontrolAn ORB withno actualeffect on thespacecraftFunnyringtonegoes offSean suggeststakingsomethingoffline that weall know won’tbeSomeonegetspagedAn FDbrutallycriticizessomeoneSomeonecomplainsabout nothavingenough coffeeSomeonementions a bestpracticesdocument thatno one knowsexistsAn ORBcaused by asimplesyntax errorSean callspeople whoare glutenfree “special”Someonebrings upstudentprankingORB causedby blindlyexecuting amanproc3 or moretotallyundefinedacronyms usedon a singleslideORB causedbycompletelydisregardingprocedureA CCITasks for asignatureAn ORBgoes fortwice as longas scheduled“BadTechnicalInput”ORBcaused byFC doinga CC taskAn ORBcaused byusing thewrong fileA CC makesa suggestthat getscompletelyshut downImpossibleaction itemsuggestedMAVENishappyPat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and ReidarAn FDblames an“FC” insteadofthemselvesSomeonefallsasleepORB causedby ignoringcheckproductsoutputSomeonesends anout of officeemailORB caused byonly one personknowing how toperform a taskSean saysORBs increaseat thebeginning ofthe semester3 or morespellingmistakes inone slideORBcaused byOASIS-PSblack magicSomeonepronouncesa CC’sname wrongSean asks aquestion with anobvious answerthat leaves theroom speechlessSomeoneassigns anaction itemto a studentORB caused bymiscommunication“PersonnelError”There’s aTDRS with one‘S’ and onewith two ‘S’s inthe same ORBSomeonetalks about“the thoughtprocess”An ORBcaused bybad versioncontrolAn ORB withno actualeffect on thespacecraftFunnyringtonegoes offSean suggeststakingsomethingoffline that weall know won’tbeSomeonegetspagedAn FDbrutallycriticizessomeoneSomeonecomplainsabout nothavingenough coffeeSomeonementions a bestpracticesdocument thatno one knowsexistsAn ORBcaused by asimplesyntax errorSean callspeople whoare glutenfree “special”Someonebrings upstudentprankingORB causedby blindlyexecuting amanproc3 or moretotallyundefinedacronyms usedon a singleslideORB causedbycompletelydisregardingprocedureA CCITasks for asignatureAn ORBgoes fortwice as longas scheduled“BadTechnicalInput”ORBcaused byFC doinga CC taskAn ORBcaused byusing thewrong fileA CC makesa suggestthat getscompletelyshut downImpossibleaction itemsuggestedMAVENishappy

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