Run a NewApplicationWritten by aThird Party withZeroDocumentationA Whole AppExists in theEcosystem andNo One ToldYou About ItBug Report thatYour LastDeployment Brokea Feature theTeam Didn't KnowExistedUser DidSomething theyRegret?Manually Edittheir ProductionChanges!Your IL Mergedyour PR withoutTesting it andNow your PMsays it's Broken"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereIT Issue isStoppedDead byClient ITDepartmentThe File isOlderthan YouAreCode that's WayMore Complicatedthan what itNeeded to be for aVery SimpleConceptDiscover aFeatureUnrelated toYour CurrentTask NeverWorked at AllClient CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter DeploymentClient Insists aFeature hasAlways Workeda Specific Waywhen it ProvablyHasn'tTheDocumentationwas Written bySomeone whoLeft theCompany"Can you make afeature like[feature thatalready exists waybetter as aseparate product]""Can you doX?" TheProjectAlreadyDoes XThe BuildBroke withoutthe TeamChangingAnythingSecretPage on aProductionSiteNo One Knows why aFeature Breaks andthe Accepted way toHandle it is toChange DatabaseValues DirectlyEveryone OnlyKnows a Pieceabout an OlderConcept orFeatureBug Report aftera Release forSomething thathas AlwaysBeen Broken"Ignore thaterror it'salways beenthere"More than 3Versions of theSame SoftwareInstalled on theSame MachineThis BugReport is aFeatureRequest inDisguiseBug Report onFeature X afterDeployment.Client Tested Xin QAEnvironment"Does anyoneknow whatversion isactually inproduction rightnow?"Run a NewApplicationWritten by aThird Party withZeroDocumentationA Whole AppExists in theEcosystem andNo One ToldYou About ItBug Report thatYour LastDeployment Brokea Feature theTeam Didn't KnowExistedUser DidSomething theyRegret?Manually Edittheir ProductionChanges!Your IL Mergedyour PR withoutTesting it andNow your PMsays it's Broken"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereIT Issue isStoppedDead byClient ITDepartmentThe File isOlderthan YouAreCode that's WayMore Complicatedthan what itNeeded to be for aVery SimpleConceptDiscover aFeatureUnrelated toYour CurrentTask NeverWorked at AllClient CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter DeploymentClient Insists aFeature hasAlways Workeda Specific Waywhen it ProvablyHasn'tTheDocumentationwas Written bySomeone whoLeft theCompany"Can you make afeature like[feature thatalready exists waybetter as aseparate product]""Can you doX?" TheProjectAlreadyDoes XThe BuildBroke withoutthe TeamChangingAnythingSecretPage on aProductionSiteNo One Knows why aFeature Breaks andthe Accepted way toHandle it is toChange DatabaseValues DirectlyEveryone OnlyKnows a Pieceabout an OlderConcept orFeatureBug Report aftera Release forSomething thathas AlwaysBeen Broken"Ignore thaterror it'salways beenthere"More than 3Versions of theSame SoftwareInstalled on theSame MachineThis BugReport is aFeatureRequest inDisguiseBug Report onFeature X afterDeployment.Client Tested Xin QAEnvironment"Does anyoneknow whatversion isactually inproduction rightnow?"

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