We shouldvalidatethat withusers firstLet’s pencil itin for furtherdiscussionlaterWe’ll need toassess thisin context ofour currentobjectivesThat couldfit in a futureroadmapiterationCan werevisit thisafter thenext sprint?This could bepart of a largerinitiative, butlet’s hold off fornowWe need toensurealignmentbefore movingforwardI’d like tohear morethoughts onthis from theteamWe shouldvalidatethat withusers firstLet’s pencil itin for furtherdiscussionlaterWe’ll need toassess thisin context ofour currentobjectivesThat couldfit in a futureroadmapiterationCan werevisit thisafter thenext sprint?This could bepart of a largerinitiative, butlet’s hold off fornowWe need toensurealignmentbefore movingforwardI’d like tohear morethoughts onthis from theteam

How to say No? - 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
  1. We should validate that with users first
  2. Let’s pencil it in for further discussion later
  3. We’ll need to assess this in context of our current objectives
  4. That could fit in a future roadmap iteration
  5. Can we revisit this after the next sprint?
  6. This could be part of a larger initiative, but let’s hold off for now
  7. We need to ensure alignment before moving forward
  8. I’d like to hear more thoughts on this from the team