Discover aFeatureUnrelated toYour CurrentTask NeverWorked at All"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereNo One Knowswhy a FeatureBreaks and theAccepted way toHandle it is toChange DatabaseValues DirectlyUser DidSomething theyRegret?Manually Edittheir ProductionChanges!A Whole AppExists in theEcosystem andNo One ToldYou About ItMore than 3Versions of theSame SoftwareInstalled on theSame MachineBug Reportafter a Releasefor Somethingthat has AlwaysBeen BrokenThe BuildBroke withoutthe TeamChangingAnything"Can you make afeature like[feature thatalready exists waybetter as aseparate product]""Can you doX?" TheProjectAlreadyDoes X"Ignore thaterror it'salwaysbeen there"Your IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenRun a NewApplicationWritten by aThird Party withZeroDocumentationEveryone OnlyKnows a Pieceabout an OlderConcept orFeatureThis BugReport is aFeatureRequest inDisguiseSecretPage on aProductionSiteClient CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter DeploymentBug Report thatYour LastDeploymentBroke a Featurethe Team Didn'tKnow ExistedCode that's WayMoreComplicated thanwhat it Needed tobe for a VerySimple ConceptClient Insists aFeature hasAlways Workeda Specific Waywhen itProvably Hasn'tIT Issue isStoppedDead byClient ITDepartmentThe File isOlderthan YouAre"Does anyoneknow whatversion isactually inproduction rightnow?"TheDocumentationwas Written bySomeone whoLeft theCompanyBug Report onFeature X afterDeployment.Client Tested Xin QAEnvironmentDiscover aFeatureUnrelated toYour CurrentTask NeverWorked at All"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereNo One Knowswhy a FeatureBreaks and theAccepted way toHandle it is toChange DatabaseValues DirectlyUser DidSomething theyRegret?Manually Edittheir ProductionChanges!A Whole AppExists in theEcosystem andNo One ToldYou About ItMore than 3Versions of theSame SoftwareInstalled on theSame MachineBug Reportafter a Releasefor Somethingthat has AlwaysBeen BrokenThe BuildBroke withoutthe TeamChangingAnything"Can you make afeature like[feature thatalready exists waybetter as aseparate product]""Can you doX?" TheProjectAlreadyDoes X"Ignore thaterror it'salwaysbeen there"Your IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenRun a NewApplicationWritten by aThird Party withZeroDocumentationEveryone OnlyKnows a Pieceabout an OlderConcept orFeatureThis BugReport is aFeatureRequest inDisguiseSecretPage on aProductionSiteClient CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter DeploymentBug Report thatYour LastDeploymentBroke a Featurethe Team Didn'tKnow ExistedCode that's WayMoreComplicated thanwhat it Needed tobe for a VerySimple ConceptClient Insists aFeature hasAlways Workeda Specific Waywhen itProvably Hasn'tIT Issue isStoppedDead byClient ITDepartmentThe File isOlderthan YouAre"Does anyoneknow whatversion isactually inproduction rightnow?"TheDocumentationwas Written bySomeone whoLeft theCompanyBug Report onFeature X afterDeployment.Client Tested Xin QAEnvironment

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