"Can you make afeature like[feature thatalready exists waybetter as aseparate product]"Bug Report thatYour LastDeploymentBroke a Featurethe Team Didn'tKnow Existed"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereSecretPage on aProductionSiteClient CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter DeploymentEveryone OnlyKnows a Pieceabout an OlderConcept orFeatureDiscover aFeatureUnrelated toYour CurrentTask NeverWorked at AllBug Report onFeature X afterDeployment.Client Tested Xin QAEnvironment"Ignore thaterror it'salwaysbeen there""Does anyoneknow whatversion isactually inproduction rightnow?"This BugReport is aFeatureRequest inDisguiseYour IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenNo One Knowswhy a FeatureBreaks and theAccepted way toHandle it is toChange DatabaseValues DirectlyA Whole AppExists in theEcosystem andNo One ToldYou About It"Can you doX?" TheProjectAlreadyDoes XTheDocumentationwas Written bySomeone whoLeft theCompanyThe BuildBroke withoutthe TeamChangingAnythingUser DidSomething theyRegret?Manually Edittheir ProductionChanges!Run a NewApplicationWritten by aThird Party withZeroDocumentationThe File isOlderthan YouAreBug Reportafter a Releasefor Somethingthat has AlwaysBeen BrokenMore than 3Versions of theSame SoftwareInstalled on theSame MachineClient Insists aFeature hasAlways Workeda Specific Waywhen itProvably Hasn'tCode that's WayMoreComplicated thanwhat it Needed tobe for a VerySimple ConceptIT Issue isStoppedDead byClient ITDepartment"Can you make afeature like[feature thatalready exists waybetter as aseparate product]"Bug Report thatYour LastDeploymentBroke a Featurethe Team Didn'tKnow Existed"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereSecretPage on aProductionSiteClient CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter DeploymentEveryone OnlyKnows a Pieceabout an OlderConcept orFeatureDiscover aFeatureUnrelated toYour CurrentTask NeverWorked at AllBug Report onFeature X afterDeployment.Client Tested Xin QAEnvironment"Ignore thaterror it'salwaysbeen there""Does anyoneknow whatversion isactually inproduction rightnow?"This BugReport is aFeatureRequest inDisguiseYour IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenNo One Knowswhy a FeatureBreaks and theAccepted way toHandle it is toChange DatabaseValues DirectlyA Whole AppExists in theEcosystem andNo One ToldYou About It"Can you doX?" TheProjectAlreadyDoes XTheDocumentationwas Written bySomeone whoLeft theCompanyThe BuildBroke withoutthe TeamChangingAnythingUser DidSomething theyRegret?Manually Edittheir ProductionChanges!Run a NewApplicationWritten by aThird Party withZeroDocumentationThe File isOlderthan YouAreBug Reportafter a Releasefor Somethingthat has AlwaysBeen BrokenMore than 3Versions of theSame SoftwareInstalled on theSame MachineClient Insists aFeature hasAlways Workeda Specific Waywhen itProvably Hasn'tCode that's WayMoreComplicated thanwhat it Needed tobe for a VerySimple ConceptIT Issue isStoppedDead byClient ITDepartment

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