(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
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
Contributed to a high visibility feature
Discovered a productivity hack that isn’t in the docs
Paired with another engineer to solve a problem
Suggested a process change that was adopted
Learned a non-technical skill that helped your job
Represented the team in a leadership meeting
Participated in GED, won, and pushed it to prod
Mentored an engineer
Left more than 15 comments on a PR
Found a better way of working by watching someone else
Reduced tech debt in the codebase
Attended a conference or workshop
Participated in a hackathon with colleagues
Led a knowledge sharing session
Shared a playlist or song that boosted productivity
Answered a “how do I…” question in Slack/Teams that helped multiple people
Solved a bug minutes before a meeting
Learned a new keyboard shortcut that changed your life
Took on a role outside your comfort zone
Presented work in a team or org-wide demo
Had a “Eureka!” moment while showering or commuting
Led a cross-team effort
Wrote or improved a TDD
Made a joke in a standup that lightened the mood
Used an analogy to explain a tech concept that made people laugh
Presented to more than 10 people >3 times
Modeled vulnerability by admitting you didn’t know something
Broke prod (and fixed it!)
Paired on debugging for over an hour without giving up
Advocated for someone else’s idea
Took part in a book club or study group at work
Reviewed a PR
Automated a manual task
Named a feature or internal tool
Participated in a themed standup or dress-up day
a moment you almost quit and what you learned from it
Advocated for an engineer’s promotion or recognition
Asked “why” three times in a discussion to understand deeper context