(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
39
40
41
42
43
44
45
46
47
48
No confluence requirements
Requirements on conflu without requirements
yzx: "Ask xyz" - xyz doesn't know
"We don't like the complex feel" - excel like wireframes
"I can't download the SVG" - cit dev to ux reg. UI files
Business agrees but devs don't
"Sorry what is this for?" cit operations during their new platform presentation
"We would like it like excel"
"Users won't understand if we don't do F" dev deem F impossible
UX gathers requirements - "Who told you this??"
"I don't like it, I want it like my bank" - cit. not a stakeholder
"Why are we in this call?"
"This is no longer for day 1"
"We don't have info on this"
"We don't need that edge case" 3 weeks before you are asked to design that edge case
"I know you are UX but we don't like it" - cit. not a stakeholder
"we need to circle back on this"
"I know research found A but you know how research is"
"Scrap A, we need B"(unclear requirements)
"seen at 16:10, 10 days ago"
"We would like it but we don't know if it'll work"
Writes req. on conflu, leaves completely different comments on figma
"This screen has been descoped" but you learn it from a screenshot of a 1:1 chat in outlook after 4 weeks
"A was actually good but simplify it"
"We need A (limited req., 10 nice to have)"
"We'll do it in post- foundation" screen never to be heard of again
"But why not do it this way" proceeds to suggest the exact same design from first review.
"This screen has been descoped"
"This is something we need to consider" - no signs of life for 3 weeks
"Ask zyx" - zyx sends to yzx.
"Third page with different req. appears in conflu"
"why are there two different req lists?"
"It's just different naming :)"
"why did you make it like this, no one does this" - cit. dev to UX
"do you have an epic for this change" cit. dev on already agreed ux
"It would take too long to gather"
Proceeds to requests D at the last minute
"Scrap B, we need C" (but no req.)
"I can get someone to email you" sends a completely different topic
"We don't have time" - requests to revert to original ux design 5 months after handover
"What color is this supposed to be" - cit. dev to UX
"I find this confusing"
"We realised we don't have an API for this" (handover was 3 months ago)
"C is too complicated, we need to circle back"
"Who requested this?"
"No, we actually don't want this" after req. showed it for 3 months.
deadline is for yesterday
"It's impossible to know it"
"I don't know but I would like it like this" - cit not a stakeholder
