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

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