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