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

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