MAVENishappyA CCITasks for asignatureA CC makesa suggestthat getscompletelyshut downSean suggeststakingsomethingoffline that weall know won’tbeSomeonetalks about“the thoughtprocess”Sean callspeople whoare glutenfree “special”An ORB withno actualeffect on thespacecraftSean saysORBs increaseat thebeginning ofthe semesterFunnyringtonegoes off“PersonnelError”There’s aTDRS with one‘S’ and onewith two ‘S’s inthe same ORB3 or morespellingmistakes inone slideORB caused bymiscommunication“BadTechnicalInput”ORB causedbycompletelydisregardingprocedureORB caused byonly one personknowing how toperform a taskSomeonebrings upstudentprankingORB causedby ignoringcheckproductsoutputImpossibleaction itemsuggestedORB causedby blindlyexecuting amanprocORBcaused byFC doinga CC taskSomeonegetspagedSean asks aquestion with anobvious answerthat leaves theroom speechlessAn ORBcaused by asimplesyntax errorORBcaused byOASIS-PSblack magicSomeoneassigns anaction itemto a studentSomeonementions a bestpracticesdocument thatno one knowsexistsSomeonefallsasleepAn FDblames an“FC” insteadofthemselvesSomeonecomplainsabout nothavingenough coffeeSomeonesends anout of officeemailPat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and ReidarAn ORBcaused bybad versioncontrolAn FDbrutallycriticizessomeoneSomeonepronouncesa CC’sname wrongAn ORBcaused byusing thewrong file3 or moretotallyundefinedacronyms usedon a singleslideAn ORBgoes fortwice as longas scheduledMAVENishappyA CCITasks for asignatureA CC makesa suggestthat getscompletelyshut downSean suggeststakingsomethingoffline that weall know won’tbeSomeonetalks about“the thoughtprocess”Sean callspeople whoare glutenfree “special”An ORB withno actualeffect on thespacecraftSean saysORBs increaseat thebeginning ofthe semesterFunnyringtonegoes off“PersonnelError”There’s aTDRS with one‘S’ and onewith two ‘S’s inthe same ORB3 or morespellingmistakes inone slideORB caused bymiscommunication“BadTechnicalInput”ORB causedbycompletelydisregardingprocedureORB caused byonly one personknowing how toperform a taskSomeonebrings upstudentprankingORB causedby ignoringcheckproductsoutputImpossibleaction itemsuggestedORB causedby blindlyexecuting amanprocORBcaused byFC doinga CC taskSomeonegetspagedSean asks aquestion with anobvious answerthat leaves theroom speechlessAn ORBcaused by asimplesyntax errorORBcaused byOASIS-PSblack magicSomeoneassigns anaction itemto a studentSomeonementions a bestpracticesdocument thatno one knowsexistsSomeonefallsasleepAn FDblames an“FC” insteadofthemselvesSomeonecomplainsabout nothavingenough coffeeSomeonesends anout of officeemailPat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and ReidarAn ORBcaused bybad versioncontrolAn FDbrutallycriticizessomeoneSomeonepronouncesa CC’sname wrongAn ORBcaused byusing thewrong file3 or moretotallyundefinedacronyms usedon a singleslideAn ORBgoes fortwice as longas scheduled

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