Bug Report onFeature X afterDeployment.Client Tested Xin QAEnvironmentIT Issue isStoppedDead byClient ITDepartmentThis BugReport is aFeatureRequest inDisguise"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereThe BuildBroke withoutthe TeamChangingAnythingMore than 3Versions of theSame SoftwareInstalled on theSame MachineDiscover aFeatureUnrelated toYour CurrentTask NeverWorked at AllRun a NewApplicationWritten by aThird Party withZeroDocumentation"Can you doX?" TheProjectAlreadyDoes XEveryone OnlyKnows a Pieceabout an OlderConcept orFeatureNo One Knows why aFeature Breaks andthe Accepted way toHandle it is toChange DatabaseValues DirectlyYour IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenSecretPage on aProductionSite"Can you make afeature like[feature thatalready exists waybetter as aseparate product]"Client CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter Deployment"Does anyoneknow whatversion isactually inproduction rightnow?"Bug Report aftera Release forSomething thathas AlwaysBeen Broken"Ignore thaterror it'salways beenthere"User DidSomething theyRegret?Manually Edittheir ProductionChanges!A Whole AppExists in theEcosystem andNo One ToldYou About ItCode that's WayMore Complicatedthan what itNeeded to be for aVery SimpleConceptTheDocumentationwas Written bySomeone whoLeft theCompanyClient Insists aFeature hasAlways Workeda Specific Waywhen it ProvablyHasn'tBug Report thatYour LastDeployment Brokea Feature theTeam Didn't KnowExistedThe File isOlderthan YouAreBug Report onFeature X afterDeployment.Client Tested Xin QAEnvironmentIT Issue isStoppedDead byClient ITDepartmentThis BugReport is aFeatureRequest inDisguise"//TODO Fix"has beenCommittedLonger thanYou've WorkedHereThe BuildBroke withoutthe TeamChangingAnythingMore than 3Versions of theSame SoftwareInstalled on theSame MachineDiscover aFeatureUnrelated toYour CurrentTask NeverWorked at AllRun a NewApplicationWritten by aThird Party withZeroDocumentation"Can you doX?" TheProjectAlreadyDoes XEveryone OnlyKnows a Pieceabout an OlderConcept orFeatureNo One Knows why aFeature Breaks andthe Accepted way toHandle it is toChange DatabaseValues DirectlyYour IL Mergedyour PR withoutTesting it andNow your PMsays it's BrokenSecretPage on aProductionSite"Can you make afeature like[feature thatalready exists waybetter as aseparate product]"Client CompletelyMisunderstood aProposed Changeand wants aRollback or Patchafter Deployment"Does anyoneknow whatversion isactually inproduction rightnow?"Bug Report aftera Release forSomething thathas AlwaysBeen Broken"Ignore thaterror it'salways beenthere"User DidSomething theyRegret?Manually Edittheir ProductionChanges!A Whole AppExists in theEcosystem andNo One ToldYou About ItCode that's WayMore Complicatedthan what itNeeded to be for aVery SimpleConceptTheDocumentationwas Written bySomeone whoLeft theCompanyClient Insists aFeature hasAlways Workeda Specific Waywhen it ProvablyHasn'tBug Report thatYour LastDeployment Brokea Feature theTeam Didn't KnowExistedThe File isOlderthan YouAre

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