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

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