"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereUser DidSomething theyRegret?Manually Edittheir ProductionChanges!Bug Report onFeature X afterDeployment.Client Tested Xin QAEnvironment"Can you make afeature like[feature thatalready exists waybetter as aseparate product]"Code that's WayMore Complicatedthan what itNeeded to be for aVery SimpleConcept"Does anyoneknow whatversion isactually inproduction rightnow?"More than 3Versions of theSame SoftwareInstalled on theSame MachineIT Issue isStoppedDead byClient ITDepartmentYour IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenNo One Knows why aFeature Breaks andthe Accepted way toHandle it is toChange DatabaseValues DirectlyThe BuildBroke withoutthe TeamChangingAnythingA Whole AppExists in theEcosystem andNo One ToldYou About It"Ignore thaterror it'salways beenthere"Everyone OnlyKnows a Pieceabout an OlderConcept orFeatureClient Insists aFeature hasAlways Workeda Specific Waywhen it ProvablyHasn'tTheDocumentationwas Written bySomeone whoLeft theCompanyClient CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter DeploymentDiscover aFeatureUnrelated toYour CurrentTask NeverWorked at AllThe File isOlderthan YouAreBug Report aftera Release forSomething thathas AlwaysBeen BrokenRun a NewApplicationWritten by aThird Party withZeroDocumentationBug Report thatYour LastDeployment Brokea Feature theTeam Didn't KnowExisted"Can you doX?" TheProjectAlreadyDoes XSecretPage on aProductionSiteThis BugReport is aFeatureRequest inDisguise"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereUser DidSomething theyRegret?Manually Edittheir ProductionChanges!Bug Report onFeature X afterDeployment.Client Tested Xin QAEnvironment"Can you make afeature like[feature thatalready exists waybetter as aseparate product]"Code that's WayMore Complicatedthan what itNeeded to be for aVery SimpleConcept"Does anyoneknow whatversion isactually inproduction rightnow?"More than 3Versions of theSame SoftwareInstalled on theSame MachineIT Issue isStoppedDead byClient ITDepartmentYour IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenNo One Knows why aFeature Breaks andthe Accepted way toHandle it is toChange DatabaseValues DirectlyThe BuildBroke withoutthe TeamChangingAnythingA Whole AppExists in theEcosystem andNo One ToldYou About It"Ignore thaterror it'salways beenthere"Everyone OnlyKnows a Pieceabout an OlderConcept orFeatureClient Insists aFeature hasAlways Workeda Specific Waywhen it ProvablyHasn'tTheDocumentationwas Written bySomeone whoLeft theCompanyClient CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter DeploymentDiscover aFeatureUnrelated toYour CurrentTask NeverWorked at AllThe File isOlderthan YouAreBug Report aftera Release forSomething thathas AlwaysBeen BrokenRun a NewApplicationWritten by aThird Party withZeroDocumentationBug Report thatYour LastDeployment Brokea Feature theTeam Didn't KnowExisted"Can you doX?" TheProjectAlreadyDoes XSecretPage on aProductionSiteThis BugReport is aFeatureRequest inDisguise

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