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