"Third pagewith differentreq. appearsin conflu"Proceedsto requestsD at thelast minute"A wasactuallygood butsimplify it""I can'tdownloadthe SVG" -cit dev to uxreg. UI filesdeadlineis foryesterday"This screen hasbeen descoped"but you learn itfrom a screenshotof a 1:1 chat inoutlook after 4weeks"We need A(limited req.,10 nice tohave)""We don't havetime" - requeststo revert tooriginal uxdesign 5 monthsafter handoverRequirementson confluwithoutrequirements"I find thisconfusing""seen at16:10, 10days ago""We don't needthat edge case"3 weeks beforeyou are askedto design thatedge case"I don't knowbut I wouldlike it likethis" - cit nota stakeholder"This isno longerfor day 1""This issomething weneed toconsider" - nosigns of life for3 weeks"Scrap B,we needC" (but noreq.)"We don't likethe complexfeel" - excellikewireframesWrites req. onconflu, leavescompletelydifferentcomments onfigma"why did youmake it likethis, no onedoes this" -cit. dev to UXUX gathersrequirements- "Who toldyou this??""Ask zyx"- zyxsends toyzx."It'simpossibleto know it""I know youare UX butwe don't likeit" - cit. not astakeholder"We don'thave infoon this""Sorry what isthis for?" citoperationsduring theirnew platformpresentation"Users won'tunderstand ifwe don't doF" dev deemF impossible"C is toocomplicated,we need tocircle back"Noconfluencerequirements"I knowresearchfound A butyou know howresearch is""But why not do itthis way"proceeds tosuggest the exactsame designfrom first review."Thisscreenhas beendescoped"yzx: "Askxyz" - xyzdoesn'tknow"we needto circleback onthis""No, weactually don'twant this" afterreq. showed itfor 3 months."We realisedwe don't havean API for this"(handover was3 months ago)"why are theretwo differentreq lists?""It's justdifferentnaming :)""What coloris thissupposed tobe" - cit. devto UX"Whorequestedthis?"Businessagreesbut devsdon't"Wewould likeit likeexcel""I can getsomeone toemail you"sends acompletelydifferent topic"Why arewe in thiscall?""We'll do it inpost-foundation"screen never tobe heard ofagain"We wouldlike it but wedon't know ifit'll work""do you havean epic for thischange" cit.dev on alreadyagreed ux"Scrap A, weneed B"(unclearrequirements)"It wouldtake toolong togather""I don't like it,I want it likemy bank" -cit. not astakeholder"Third pagewith differentreq. appearsin conflu"Proceedsto requestsD at thelast minute"A wasactuallygood butsimplify it""I can'tdownloadthe SVG" -cit dev to uxreg. UI filesdeadlineis foryesterday"This screen hasbeen descoped"but you learn itfrom a screenshotof a 1:1 chat inoutlook after 4weeks"We need A(limited req.,10 nice tohave)""We don't havetime" - requeststo revert tooriginal uxdesign 5 monthsafter handoverRequirementson confluwithoutrequirements"I find thisconfusing""seen at16:10, 10days ago""We don't needthat edge case"3 weeks beforeyou are askedto design thatedge case"I don't knowbut I wouldlike it likethis" - cit nota stakeholder"This isno longerfor day 1""This issomething weneed toconsider" - nosigns of life for3 weeks"Scrap B,we needC" (but noreq.)"We don't likethe complexfeel" - excellikewireframesWrites req. onconflu, leavescompletelydifferentcomments onfigma"why did youmake it likethis, no onedoes this" -cit. dev to UXUX gathersrequirements- "Who toldyou this??""Ask zyx"- zyxsends toyzx."It'simpossibleto know it""I know youare UX butwe don't likeit" - cit. not astakeholder"We don'thave infoon this""Sorry what isthis for?" citoperationsduring theirnew platformpresentation"Users won'tunderstand ifwe don't doF" dev deemF impossible"C is toocomplicated,we need tocircle back"Noconfluencerequirements"I knowresearchfound A butyou know howresearch is""But why not do itthis way"proceeds tosuggest the exactsame designfrom first review."Thisscreenhas beendescoped"yzx: "Askxyz" - xyzdoesn'tknow"we needto circleback onthis""No, weactually don'twant this" afterreq. showed itfor 3 months."We realisedwe don't havean API for this"(handover was3 months ago)"why are theretwo differentreq lists?""It's justdifferentnaming :)""What coloris thissupposed tobe" - cit. devto UX"Whorequestedthis?"Businessagreesbut devsdon't"Wewould likeit likeexcel""I can getsomeone toemail you"sends acompletelydifferent topic"Why arewe in thiscall?""We'll do it inpost-foundation"screen never tobe heard ofagain"We wouldlike it but wedon't know ifit'll work""do you havean epic for thischange" cit.dev on alreadyagreed ux"Scrap A, weneed B"(unclearrequirements)"It wouldtake toolong togather""I don't like it,I want it likemy bank" -cit. not astakeholder

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