Bug Report onFeature X afterDeployment.Client Tested Xin QAEnvironmentMore than 3Versions of theSame SoftwareInstalled on theSame MachineRun a NewApplicationWritten by aThird Party withZeroDocumentation"Can you doX?" TheProjectAlreadyDoes XBug Report thatYour LastDeployment Brokea Feature theTeam Didn't KnowExistedA Whole AppExists in theEcosystem andNo One ToldYou About ItBug Report aftera Release forSomething thathas AlwaysBeen BrokenThis BugReport is aFeatureRequest inDisguise"Can you make afeature like[feature thatalready exists waybetter as aseparate product]"SecretPage on aProductionSiteDiscover aFeatureUnrelated toYour CurrentTask NeverWorked at AllClient Insists aFeature hasAlways Workeda Specific Waywhen it ProvablyHasn'tClient CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter Deployment"Ignore thaterror it'salways beenthere"Everyone OnlyKnows a Pieceabout an OlderConcept orFeatureTheDocumentationwas Written bySomeone whoLeft theCompanyUser DidSomething theyRegret?Manually Edittheir ProductionChanges!Your IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenThe File isOlderthan YouAreThe BuildBroke withoutthe TeamChangingAnything"Does anyoneknow whatversion isactually inproduction rightnow?"Code that's WayMore Complicatedthan what itNeeded to be for aVery SimpleConcept"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereIT Issue isStoppedDead byClient ITDepartmentNo One Knows why aFeature Breaks andthe Accepted way toHandle it is toChange DatabaseValues DirectlyBug Report onFeature X afterDeployment.Client Tested Xin QAEnvironmentMore than 3Versions of theSame SoftwareInstalled on theSame MachineRun a NewApplicationWritten by aThird Party withZeroDocumentation"Can you doX?" TheProjectAlreadyDoes XBug Report thatYour LastDeployment Brokea Feature theTeam Didn't KnowExistedA Whole AppExists in theEcosystem andNo One ToldYou About ItBug Report aftera Release forSomething thathas AlwaysBeen BrokenThis BugReport is aFeatureRequest inDisguise"Can you make afeature like[feature thatalready exists waybetter as aseparate product]"SecretPage on aProductionSiteDiscover aFeatureUnrelated toYour CurrentTask NeverWorked at AllClient Insists aFeature hasAlways Workeda Specific Waywhen it ProvablyHasn'tClient CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter Deployment"Ignore thaterror it'salways beenthere"Everyone OnlyKnows a Pieceabout an OlderConcept orFeatureTheDocumentationwas Written bySomeone whoLeft theCompanyUser DidSomething theyRegret?Manually Edittheir ProductionChanges!Your IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenThe File isOlderthan YouAreThe BuildBroke withoutthe TeamChangingAnything"Does anyoneknow whatversion isactually inproduction rightnow?"Code that's WayMore Complicatedthan what itNeeded to be for aVery SimpleConcept"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereIT Issue isStoppedDead byClient ITDepartmentNo 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. Bug Report on Feature X after Deployment. Client Tested X in QA Environment
  2. More than 3 Versions of the Same Software Installed on the Same Machine
  3. Run a New Application Written by a Third Party with Zero Documentation
  4. "Can you do X?" The Project Already Does X
  5. Bug Report that Your Last Deployment Broke a Feature the Team Didn't Know Existed
  6. A Whole App Exists in the Ecosystem and No One Told You About It
  7. Bug Report after a Release for Something that has Always Been Broken
  8. This Bug Report is a Feature Request in Disguise
  9. "Can you make a feature like [feature that already exists way better as a separate product]"
  10. Secret Page on a Production Site
  11. Discover a Feature Unrelated to Your Current Task Never Worked at All
  12. Client Insists a Feature has Always Worked a Specific Way when it Provably Hasn't
  13. Client Completely Misunderstood a Proposed Change and wants a Rollback or Patch after Deployment
  14. "Ignore that error it's always been there"
  15. Everyone Only Knows a Piece about an Older Concept or Feature
  16. The Documentation was Written by Someone who Left the Company
  17. User Did Something they Regret? Manually Edit their Production Changes!
  18. Your IL Merged your PR without Testing it and Now your PM says it's Broken
  19. The File is Older than You Are
  20. The Build Broke without the Team Changing Anything
  21. "Does anyone know what version is actually in production right now?"
  22. Code that's Way More Complicated than what it Needed to be for a Very Simple Concept
  23. "//TODO Fix" has been Committed Longer than You've Worked Here
  24. IT Issue is Stopped Dead by Client IT Department
  25. No One Knows why a Feature Breaks and the Accepted way to Handle it is to Change Database Values Directly