Can yourepeatthat?Ramble/BabbleDataRaptorPORollCallYou'reonMuteDemonotapprovedPingContinuosImprovement*RedStarThingy SomeonesaysBINGO!Someonesharesphoto oftheir kidSnortYou beingRetroMVPWrong tabclosed indemoThat'sa bugJustenough tobedangerousRollingoffprojectI will takethesilenceas...RE-SpiteWalk/Takethat back.. KiaSpeaksNon-MVPMVPYes NewStoryHow doesthat workin CB?AssessmentCase CaseSomeonekick offrecording?Out oftheBoxForExample BandwidthResponsefrom MelsemailCan yourepeatthat?Ramble/BabbleDataRaptorPORollCallYou'reonMuteDemonotapprovedPingContinuosImprovement*RedStarThingySomeonesaysBINGO!Someonesharesphoto oftheir kidSnortYou beingRetroMVPWrong tabclosed indemoThat'sa bugJustenough tobedangerousRollingoffprojectI will takethesilenceas...RE-SpiteWalk/Takethat back.. KiaSpeaksNon-MVPMVPYesNewStoryHow doesthat workin CB?AssessmentCase CaseSomeonekick offrecording?Out oftheBoxForExampleBandwidthResponsefrom Melsemail

R&R - 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
  1. Can you repeat that?
  2. Ramble/Babble
  3. Data Raptor
  4. PO Roll Call
  5. You're on Mute
  6. Demo not approved
  7. Ping
  8. Continuos Improvement
  9. *Red Star Thingy
  10. Someone says BINGO!
  11. Someone shares photo of their kid
  12. Snort
  13. You being Retro MVP
  14. Wrong tab closed in demo
  15. That's a bug
  16. Just enough to be dangerous
  17. Rolling off project
  18. I will take the silence as...
  19. RE-Spite
  20. Walk/Take that back..
  21. Kia Speaks
  22. Non-MVP
  23. MVP Yes
  24. New Story
  25. How does that work in CB?
  26. Assessment Case Case
  27. Someone kick off recording?
  28. Out of the Box
  29. For Example
  30. Bandwidth
  31. Response from Mels email