IT Issue isStoppedDead byClient ITDepartmentMore than 3Versions of theSame SoftwareInstalled on theSame MachineClient CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter DeploymentBug Report thatYour LastDeployment Brokea Feature theTeam Didn't KnowExistedUser DidSomething theyRegret?Manually Edittheir ProductionChanges!The BuildBroke withoutthe TeamChangingAnythingClient Insists aFeature hasAlways Workeda Specific Waywhen it ProvablyHasn'tEveryone OnlyKnows a Pieceabout an OlderConcept orFeatureTheDocumentationwas Written bySomeone whoLeft theCompany"Can you make afeature like[feature thatalready exists waybetter as aseparate product]"A Whole AppExists in theEcosystem andNo One ToldYou About It"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereThe File isOlderthan YouAreRun a NewApplicationWritten by aThird Party withZeroDocumentationNo One Knows why aFeature Breaks andthe Accepted way toHandle it is toChange DatabaseValues DirectlyYour IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenBug Report aftera Release forSomething thathas AlwaysBeen BrokenBug Report onFeature X afterDeployment.Client Tested Xin QAEnvironment"Can you doX?" TheProjectAlreadyDoes XCode that's WayMore Complicatedthan what itNeeded to be for aVery SimpleConcept"Does anyoneknow whatversion isactually inproduction rightnow?""Ignore thaterror it'salways beenthere"SecretPage on aProductionSiteDiscover aFeatureUnrelated toYour CurrentTask NeverWorked at AllThis BugReport is aFeatureRequest inDisguiseIT Issue isStoppedDead byClient ITDepartmentMore than 3Versions of theSame SoftwareInstalled on theSame MachineClient CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter DeploymentBug Report thatYour LastDeployment Brokea Feature theTeam Didn't KnowExistedUser DidSomething theyRegret?Manually Edittheir ProductionChanges!The BuildBroke withoutthe TeamChangingAnythingClient Insists aFeature hasAlways Workeda Specific Waywhen it ProvablyHasn'tEveryone OnlyKnows a Pieceabout an OlderConcept orFeatureTheDocumentationwas Written bySomeone whoLeft theCompany"Can you make afeature like[feature thatalready exists waybetter as aseparate product]"A Whole AppExists in theEcosystem andNo One ToldYou About It"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereThe File isOlderthan YouAreRun a NewApplicationWritten by aThird Party withZeroDocumentationNo One Knows why aFeature Breaks andthe Accepted way toHandle it is toChange DatabaseValues DirectlyYour IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenBug Report aftera Release forSomething thathas AlwaysBeen BrokenBug Report onFeature X afterDeployment.Client Tested Xin QAEnvironment"Can you doX?" TheProjectAlreadyDoes XCode that's WayMore Complicatedthan what itNeeded to be for aVery SimpleConcept"Does anyoneknow whatversion isactually inproduction rightnow?""Ignore thaterror it'salways beenthere"SecretPage on aProductionSiteDiscover aFeatureUnrelated toYour CurrentTask NeverWorked at AllThis BugReport is aFeatureRequest inDisguise

This is Fine - 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
  1. IT Issue is Stopped Dead by Client IT Department
  2. More than 3 Versions of the Same Software Installed on the Same Machine
  3. Client Completely Misunderstood a Proposed Change and wants a Rollback or Patch after Deployment
  4. Bug Report that Your Last Deployment Broke a Feature the Team Didn't Know Existed
  5. User Did Something they Regret? Manually Edit their Production Changes!
  6. The Build Broke without the Team Changing Anything
  7. Client Insists a Feature has Always Worked a Specific Way when it Provably Hasn't
  8. Everyone Only Knows a Piece about an Older Concept or Feature
  9. The Documentation was Written by Someone who Left the Company
  10. "Can you make a feature like [feature that already exists way better as a separate product]"
  11. A Whole App Exists in the Ecosystem and No One Told You About It
  12. "//TODO Fix" has been Committed Longer than You've Worked Here
  13. The File is Older than You Are
  14. Run a New Application Written by a Third Party with Zero Documentation
  15. No One Knows why a Feature Breaks and the Accepted way to Handle it is to Change Database Values Directly
  16. Your IL Merged your PR without Testing it and Now your PM says it's Broken
  17. Bug Report after a Release for Something that has Always Been Broken
  18. Bug Report on Feature X after Deployment. Client Tested X in QA Environment
  19. "Can you do X?" The Project Already Does X
  20. Code that's Way More Complicated than what it Needed to be for a Very Simple Concept
  21. "Does anyone know what version is actually in production right now?"
  22. "Ignore that error it's always been there"
  23. Secret Page on a Production Site
  24. Discover a Feature Unrelated to Your Current Task Never Worked at All
  25. This Bug Report is a Feature Request in Disguise