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