User DidSomething theyRegret?Manually Edittheir ProductionChanges!"Can you make afeature like[feature thatalready exists waybetter as aseparate product]"Client Insists aFeature hasAlways Workeda Specific Waywhen it ProvablyHasn'tIT Issue isStoppedDead byClient ITDepartmentDiscover aFeatureUnrelated toYour CurrentTask NeverWorked at AllClient CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter DeploymentEveryone OnlyKnows a Pieceabout an OlderConcept orFeatureCode that's WayMore Complicatedthan what itNeeded to be for aVery SimpleConcept"Can you doX?" TheProjectAlreadyDoes XBug Report thatYour LastDeployment Brokea Feature theTeam Didn't KnowExistedBug Report onFeature X afterDeployment.Client Tested Xin QAEnvironmentA Whole AppExists in theEcosystem andNo One ToldYou About ItThe File isOlderthan YouAreThis BugReport is aFeatureRequest inDisguiseMore than 3Versions of theSame SoftwareInstalled on theSame MachineTheDocumentationwas Written bySomeone whoLeft theCompanyThe BuildBroke withoutthe TeamChangingAnything"Does anyoneknow whatversion isactually inproduction rightnow?"Your IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenRun a NewApplicationWritten by aThird Party withZeroDocumentation"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereSecretPage on aProductionSiteNo One Knows why aFeature Breaks andthe Accepted way toHandle it is toChange DatabaseValues Directly"Ignore thaterror it'salways beenthere"Bug Report aftera Release forSomething thathas AlwaysBeen BrokenUser DidSomething theyRegret?Manually Edittheir ProductionChanges!"Can you make afeature like[feature thatalready exists waybetter as aseparate product]"Client Insists aFeature hasAlways Workeda Specific Waywhen it ProvablyHasn'tIT Issue isStoppedDead byClient ITDepartmentDiscover aFeatureUnrelated toYour CurrentTask NeverWorked at AllClient CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter DeploymentEveryone OnlyKnows a Pieceabout an OlderConcept orFeatureCode that's WayMore Complicatedthan what itNeeded to be for aVery SimpleConcept"Can you doX?" TheProjectAlreadyDoes XBug Report thatYour LastDeployment Brokea Feature theTeam Didn't KnowExistedBug Report onFeature X afterDeployment.Client Tested Xin QAEnvironmentA Whole AppExists in theEcosystem andNo One ToldYou About ItThe File isOlderthan YouAreThis BugReport is aFeatureRequest inDisguiseMore than 3Versions of theSame SoftwareInstalled on theSame MachineTheDocumentationwas Written bySomeone whoLeft theCompanyThe BuildBroke withoutthe TeamChangingAnything"Does anyoneknow whatversion isactually inproduction rightnow?"Your IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenRun a NewApplicationWritten by aThird Party withZeroDocumentation"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereSecretPage on aProductionSiteNo One Knows why aFeature Breaks andthe Accepted way toHandle it is toChange DatabaseValues Directly"Ignore thaterror it'salways beenthere"Bug Report aftera Release forSomething thathas AlwaysBeen Broken

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