“PersonnelError”“BadTechnicalInput”Sean callspeople whoare glutenfree “special”3 or morespellingmistakes inone slideORBcaused byOASIS-PSblack magicA CCITasks for asignatureORB causedby blindlyexecuting amanprocPat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and ReidarAn ORBcaused by asimplesyntax errorSomeoneassigns anaction itemto a studentSomeonefallsasleepORB caused bymiscommunicationSomeonegetspagedSomeonementions a bestpracticesdocument thatno one knowsexists3 or moretotallyundefinedacronyms usedon a singleslideAn ORBgoes fortwice as longas scheduledAn ORBcaused byusing thewrong fileSomeonepronouncesa CC’sname wrongImpossibleaction itemsuggestedMAVENishappyFunnyringtonegoes offSomeonetalks about“the thoughtprocess”Sean asks aquestion with anobvious answerthat leaves theroom speechlessSomeonesends anout of officeemailSomeonebrings upstudentprankingSomeonecomplainsabout nothavingenough coffeeThere’s aTDRS with one‘S’ and onewith two ‘S’s inthe same ORBA CC makesa suggestthat getscompletelyshut downORB causedby ignoringcheckproductsoutputAn FDblames an“FC” insteadofthemselvesORB caused byonly one personknowing how toperform a taskAn ORBcaused bybad versioncontrolAn ORB withno actualeffect on thespacecraftSean saysORBs increaseat thebeginning ofthe semesterSean suggeststakingsomethingoffline that weall know won’tbeORBcaused byFC doinga CC taskAn FDbrutallycriticizessomeoneORB causedbycompletelydisregardingprocedure“PersonnelError”“BadTechnicalInput”Sean callspeople whoare glutenfree “special”3 or morespellingmistakes inone slideORBcaused byOASIS-PSblack magicA CCITasks for asignatureORB causedby blindlyexecuting amanprocPat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and ReidarAn ORBcaused by asimplesyntax errorSomeoneassigns anaction itemto a studentSomeonefallsasleepORB caused bymiscommunicationSomeonegetspagedSomeonementions a bestpracticesdocument thatno one knowsexists3 or moretotallyundefinedacronyms usedon a singleslideAn ORBgoes fortwice as longas scheduledAn ORBcaused byusing thewrong fileSomeonepronouncesa CC’sname wrongImpossibleaction itemsuggestedMAVENishappyFunnyringtonegoes offSomeonetalks about“the thoughtprocess”Sean asks aquestion with anobvious answerthat leaves theroom speechlessSomeonesends anout of officeemailSomeonebrings upstudentprankingSomeonecomplainsabout nothavingenough coffeeThere’s aTDRS with one‘S’ and onewith two ‘S’s inthe same ORBA CC makesa suggestthat getscompletelyshut downORB causedby ignoringcheckproductsoutputAn FDblames an“FC” insteadofthemselvesORB caused byonly one personknowing how toperform a taskAn ORBcaused bybad versioncontrolAn ORB withno actualeffect on thespacecraftSean saysORBs increaseat thebeginning ofthe semesterSean suggeststakingsomethingoffline that weall know won’tbeORBcaused byFC doinga CC taskAn FDbrutallycriticizessomeoneORB causedbycompletelydisregardingprocedure

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