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

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