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

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