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