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