Doug usesoverly technicallanguage toexplainsomethingTravisrepeatsDoug; ScottmorereceptiveTerry tries tosay "yes, wecan do that"while ScottfumblesDatabasefails toload onfirst tryJaimespeaks moreslowly thanthe last threespeakersThey blametheirinconsistentdata on ourcodeFree!"Can yousee myscreen?"Travistakes offshirt oncameraDoug laughsat aninappropriatetimeMikepromisesunreasonabledeadlineRusty describes atask as UI withoutrealizing the back-end structurerequiredRusty usesesotericNavyexpletive oracronymTangentabout UIperformanceProposedsolutioncan't/won'trun on theirPC"Biobreak"Doug usesoverly technicallanguage toexplainsomethingTravisrepeatsDoug; ScottmorereceptiveTerry tries tosay "yes, wecan do that"while ScottfumblesDatabasefails toload onfirst tryJaimespeaks moreslowly thanthe last threespeakersThey blametheirinconsistentdata on ourcodeFree!"Can yousee myscreen?"Travistakes offshirt oncameraDoug laughsat aninappropriatetimeMikepromisesunreasonabledeadlineRusty describes atask as UI withoutrealizing the back-end structurerequiredRusty usesesotericNavyexpletive oracronymTangentabout UIperformanceProposedsolutioncan't/won'trun on theirPC"Biobreak"

Thursday Meeting fun - 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
  1. Doug uses overly technical language to explain something
  2. Travis repeats Doug; Scott more receptive
  3. Terry tries to say "yes, we can do that" while Scott fumbles
  4. Database fails to load on first try
  5. Jaime speaks more slowly than the last three speakers
  6. They blame their inconsistent data on our code
  7. Free!
  8. "Can you see my screen?"
  9. Travis takes off shirt on camera
  10. Doug laughs at an inappropriate time
  11. Mike promises unreasonable deadline
  12. Rusty describes a task as UI without realizing the back-end structure required
  13. Rusty uses esoteric Navy expletive or acronym
  14. Tangent about UI performance
  15. Proposed solution can't/won't run on their PC
  16. "Bio break"