Client Insists aFeature hasAlways Workeda Specific Waywhen it ProvablyHasn'tThis BugReport is aFeatureRequest inDisguise"Does anyoneknow whatversion isactually inproduction rightnow?"A Whole AppExists in theEcosystem andNo One ToldYou About ItBug Report thatYour LastDeployment Brokea Feature theTeam Didn't KnowExisted"Can you make afeature like[feature thatalready exists waybetter as aseparate product]"Your IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenUser DidSomething theyRegret?Manually Edittheir ProductionChanges!TheDocumentationwas Written bySomeone whoLeft theCompanySecretPage on aProductionSiteMore than 3Versions of theSame SoftwareInstalled on theSame MachineIT Issue isStoppedDead byClient ITDepartmentThe File isOlderthan YouAreRun a NewApplicationWritten by aThird Party withZeroDocumentationThe BuildBroke withoutthe TeamChangingAnything"Ignore thaterror it'salways beenthere"Everyone OnlyKnows a Pieceabout an OlderConcept orFeatureBug Report onFeature X afterDeployment.Client Tested Xin QAEnvironment"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereBug Report aftera Release forSomething thathas AlwaysBeen Broken"Can you doX?" TheProjectAlreadyDoes XCode that's WayMore Complicatedthan what itNeeded to be for aVery SimpleConceptClient CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter DeploymentDiscover aFeatureUnrelated toYour CurrentTask NeverWorked at AllNo One Knows why aFeature Breaks andthe Accepted way toHandle it is toChange DatabaseValues DirectlyClient Insists aFeature hasAlways Workeda Specific Waywhen it ProvablyHasn'tThis BugReport is aFeatureRequest inDisguise"Does anyoneknow whatversion isactually inproduction rightnow?"A Whole AppExists in theEcosystem andNo One ToldYou About ItBug Report thatYour LastDeployment Brokea Feature theTeam Didn't KnowExisted"Can you make afeature like[feature thatalready exists waybetter as aseparate product]"Your IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenUser DidSomething theyRegret?Manually Edittheir ProductionChanges!TheDocumentationwas Written bySomeone whoLeft theCompanySecretPage on aProductionSiteMore than 3Versions of theSame SoftwareInstalled on theSame MachineIT Issue isStoppedDead byClient ITDepartmentThe File isOlderthan YouAreRun a NewApplicationWritten by aThird Party withZeroDocumentationThe BuildBroke withoutthe TeamChangingAnything"Ignore thaterror it'salways beenthere"Everyone OnlyKnows a Pieceabout an OlderConcept orFeatureBug Report onFeature X afterDeployment.Client Tested Xin QAEnvironment"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereBug Report aftera Release forSomething thathas AlwaysBeen Broken"Can you doX?" TheProjectAlreadyDoes XCode that's WayMore Complicatedthan what itNeeded to be for aVery SimpleConceptClient CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter DeploymentDiscover aFeatureUnrelated toYour CurrentTask NeverWorked at AllNo One Knows why aFeature Breaks andthe Accepted way toHandle it is toChange DatabaseValues Directly

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