A CC makesa suggestthat getscompletelyshut down,ORB causedby ignoringcheckproductsoutput,Someonefallsasleep,Someonementions a bestpracticesdocument thatno one knowsexists,An FDbrutallycriticizessomeone,MAVENishappy,An FDblames an“FC” insteadofthemselves,“PersonnelError”,ORB caused byonly one personknowing how toperform a task,Pat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and Reidar,Someonesends anout of officeemail,An ORBcaused byusing thewrong file,Someonecomplainsabout nothavingenough coffeeORBcaused byFC doinga CC task,Sean saysORBs increaseat thebeginning ofthe semester,An ORBcaused bybad versioncontrol,Someonetalks about“the thoughtprocess”,Someonegetspaged,ORB caused bymiscommunication,ORB causedby blindlyexecuting amanproc,“BadTechnicalInput”,Sean callspeople whoare glutenfree“special”,3 or morespellingmistakes inone slide,An ORBcaused by asimplesyntax error,ORB causedbycompletelydisregardingprocedure,Sean suggeststakingsomethingoffline that weall know won’tbe,Sean asks aquestion with anobvious answerthat leaves theroom speechless,A CCITasks for asignature,3 or moretotallyundefinedacronyms usedon a singleslide,Someonepronouncesa CC’s namewrong,Funnyringtonegoes off,An ORB withno actualeffect on thespacecraft,ORB causedby OASIS-PS blackmagic,Impossibleaction itemsuggested,There’s a TDRSwith one ‘S’ andone with two‘S’s in the sameORB,Someonebrings upstudentpranking,Someoneassigns anaction itemto a student,An ORBgoes fortwice as longasscheduled,A CC makesa suggestthat getscompletelyshut down,ORB causedby ignoringcheckproductsoutput,Someonefallsasleep,Someonementions a bestpracticesdocument thatno one knowsexists,An FDbrutallycriticizessomeone,MAVENishappy,An FDblames an“FC” insteadofthemselves,“PersonnelError”,ORB caused byonly one personknowing how toperform a task,Pat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and Reidar,Someonesends anout of officeemail,An ORBcaused byusing thewrong file,Someonecomplainsabout nothavingenough coffeeORBcaused byFC doinga CC task,Sean saysORBs increaseat thebeginning ofthe semester,An ORBcaused bybad versioncontrol,Someonetalks about“the thoughtprocess”,Someonegetspaged,ORB caused bymiscommunication,ORB causedby blindlyexecuting amanproc,“BadTechnicalInput”,Sean callspeople whoare glutenfree“special”,3 or morespellingmistakes inone slide,An ORBcaused by asimplesyntax error,ORB causedbycompletelydisregardingprocedure,Sean suggeststakingsomethingoffline that weall know won’tbe,Sean asks aquestion with anobvious answerthat leaves theroom speechless,A CCITasks for asignature,3 or moretotallyundefinedacronyms usedon a singleslide,Someonepronouncesa CC’s namewrong,Funnyringtonegoes off,An ORB withno actualeffect on thespacecraft,ORB causedby OASIS-PS blackmagic,Impossibleaction itemsuggested,There’s a TDRSwith one ‘S’ andone with two‘S’s in the sameORB,Someonebrings upstudentpranking,Someoneassigns anaction itemto a student,An ORBgoes fortwice as longasscheduled,

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