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