Bug Report thatYour LastDeployment Brokea Feature theTeam Didn't KnowExistedThe BuildBroke withoutthe TeamChangingAnythingClient CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter Deployment"Can you make afeature like[feature thatalready exists waybetter as aseparate product]"Your IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenBug Report onFeature X afterDeployment.Client Tested Xin QAEnvironmentBug Report aftera Release forSomething thathas AlwaysBeen Broken"Ignore thaterror it'salways beenthere"Discover aFeatureUnrelated toYour CurrentTask NeverWorked at AllUser DidSomething theyRegret?Manually Edittheir ProductionChanges!"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereCode that's WayMore Complicatedthan what itNeeded to be for aVery SimpleConceptThe File isOlderthan YouAreSecretPage on aProductionSite"Does anyoneknow whatversion isactually inproduction rightnow?"Everyone OnlyKnows a Pieceabout an OlderConcept orFeatureNo One Knows why aFeature Breaks andthe Accepted way toHandle it is toChange DatabaseValues DirectlyIT Issue isStoppedDead byClient ITDepartmentA Whole AppExists in theEcosystem andNo One ToldYou About ItClient Insists aFeature hasAlways Workeda Specific Waywhen it ProvablyHasn't"Can you doX?" TheProjectAlreadyDoes XRun a NewApplicationWritten by aThird Party withZeroDocumentationThis BugReport is aFeatureRequest inDisguiseMore than 3Versions of theSame SoftwareInstalled on theSame MachineTheDocumentationwas Written bySomeone whoLeft theCompanyBug Report thatYour LastDeployment Brokea Feature theTeam Didn't KnowExistedThe BuildBroke withoutthe TeamChangingAnythingClient CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter Deployment"Can you make afeature like[feature thatalready exists waybetter as aseparate product]"Your IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenBug Report onFeature X afterDeployment.Client Tested Xin QAEnvironmentBug Report aftera Release forSomething thathas AlwaysBeen Broken"Ignore thaterror it'salways beenthere"Discover aFeatureUnrelated toYour CurrentTask NeverWorked at AllUser DidSomething theyRegret?Manually Edittheir ProductionChanges!"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereCode that's WayMore Complicatedthan what itNeeded to be for aVery SimpleConceptThe File isOlderthan YouAreSecretPage on aProductionSite"Does anyoneknow whatversion isactually inproduction rightnow?"Everyone OnlyKnows a Pieceabout an OlderConcept orFeatureNo One Knows why aFeature Breaks andthe Accepted way toHandle it is toChange DatabaseValues DirectlyIT Issue isStoppedDead byClient ITDepartmentA Whole AppExists in theEcosystem andNo One ToldYou About ItClient Insists aFeature hasAlways Workeda Specific Waywhen it ProvablyHasn't"Can you doX?" TheProjectAlreadyDoes XRun a NewApplicationWritten by aThird Party withZeroDocumentationThis BugReport is aFeatureRequest inDisguiseMore than 3Versions of theSame SoftwareInstalled on theSame MachineTheDocumentationwas Written bySomeone whoLeft theCompany

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