Some1 QCs their QRs some1 asks Sarah to sit w them AJ finishes first CIF comes back for Sector/Industry label XX WFH XX will be 1st question for Sarah no buttons buttoned on his shirt Some1 says MIDR QC templates R wrong Dev comes back with a snarky comment XXspends 30 min watering plants Tester send an email ending in…… Specialist will pass off his work to some1 Specialist will send a rude email XX will point out scripting is wrong Grubb yanks his hair some1 says they have too much product. Some1 says 9/30 data doesn't match XX will ask us a MIDR back up question Past Perfom footnote is not bolded somewhere tester is still out sick JHteam doesn't finish 27 reports we get expense waiver questions Someone saves over a real Prod file The scripts for BMs didn't work Some1 QCs their QRs some1 asks Sarah to sit w them AJ finishes first CIF comes back for Sector/Industry label XX WFH XX will be 1st question for Sarah no buttons buttoned on his shirt Some1 says MIDR QC templates R wrong Dev comes back with a snarky comment XXspends 30 min watering plants Tester send an email ending in…… Specialist will pass off his work to some1 Specialist will send a rude email XX will point out scripting is wrong Grubb yanks his hair some1 says they have too much product. Some1 says 9/30 data doesn't match XX will ask us a MIDR back up question Past Perfom footnote is not bolded somewhere tester is still out sick JHteam doesn't finish 27 reports we get expense waiver questions Someone saves over a real Prod file The scripts for BMs didn't work
(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.
Some1 QCs their QRs
some1 asks Sarah to sit w them
AJ finishes first
CIF comes back for Sector/Industry label
XX WFH
XX will be 1st question for Sarah
no buttons buttoned on his shirt
Some1 says MIDR QC templates R wrong
Dev comes back with a snarky comment
XXspends 30 min watering plants
Tester send an email ending in……
Specialist will pass off his work to some1
Specialist will send a rude email
XX will point out scripting is wrong
Grubb yanks his hair
some1 says they have too much product.
Some1 says 9/30 data doesn't match
XX will ask us a MIDR back up question
Past Perfom footnote is not bolded somewhere
tester is still out sick
JHteam doesn't finish 27 reports
we get expense waiver questions
Someone saves over a real Prod file
The scripts for BMs didn't work