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