Client CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter DeploymentThe File isOlderthan YouAreThe BuildBroke withoutthe TeamChangingAnythingIT Issue isStoppedDead byClient ITDepartment"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 WorkedHereNo One Knowswhy a FeatureBreaks and theAccepted way toHandle it is toChange DatabaseValues DirectlyYour IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenTheDocumentationwas Written bySomeone whoLeft theCompanyBug Report thatYour LastDeploymentBroke a Featurethe Team Didn'tKnow ExistedBug Reportafter a Releasefor Somethingthat has AlwaysBeen BrokenCode that's WayMoreComplicated thanwhat it Needed tobe for a VerySimple ConceptBug Report onFeature X afterDeployment.Client Tested Xin QAEnvironment"Can you doX?" TheProjectAlreadyDoes X"Does anyoneknow whatversion isactually inproduction rightnow?"Client Insists aFeature hasAlways Workeda Specific Waywhen itProvably Hasn'tMore than 3Versions of theSame SoftwareInstalled on theSame Machine"Ignore thaterror it'salwaysbeen there"This BugReport is aFeatureRequest inDisguiseUser DidSomething theyRegret?Manually Edittheir ProductionChanges!Everyone OnlyKnows a Pieceabout an OlderConcept orFeatureSecretPage on aProductionSiteDiscover aFeatureUnrelated toYour CurrentTask NeverWorked at AllRun a NewApplicationWritten by aThird Party withZeroDocumentationClient CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter DeploymentThe File isOlderthan YouAreThe BuildBroke withoutthe TeamChangingAnythingIT Issue isStoppedDead byClient ITDepartment"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 WorkedHereNo One Knowswhy a FeatureBreaks and theAccepted way toHandle it is toChange DatabaseValues DirectlyYour IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenTheDocumentationwas Written bySomeone whoLeft theCompanyBug Report thatYour LastDeploymentBroke a Featurethe Team Didn'tKnow ExistedBug Reportafter a Releasefor Somethingthat has AlwaysBeen BrokenCode that's WayMoreComplicated thanwhat it Needed tobe for a VerySimple ConceptBug Report onFeature X afterDeployment.Client Tested Xin QAEnvironment"Can you doX?" TheProjectAlreadyDoes X"Does anyoneknow whatversion isactually inproduction rightnow?"Client Insists aFeature hasAlways Workeda Specific Waywhen itProvably Hasn'tMore than 3Versions of theSame SoftwareInstalled on theSame Machine"Ignore thaterror it'salwaysbeen there"This BugReport is aFeatureRequest inDisguiseUser DidSomething theyRegret?Manually Edittheir ProductionChanges!Everyone OnlyKnows a Pieceabout an OlderConcept orFeatureSecretPage on aProductionSiteDiscover aFeatureUnrelated toYour CurrentTask NeverWorked at AllRun a NewApplicationWritten by aThird Party withZeroDocumentation

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