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

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