bug filed pastschemafreeze thatneeds schemachangestresseatinga P1 bugis filed onusanother teamsigned off earlyand is playingping pong veryloudlyyouwhisper“this is fine”to yourselfsomeonesuggests "justcheck it in andgive it a try" onyour story/bugnot being able toexplain to anyoneoutside ofSalesforce what'sgoing on beyondthat it's "a bigdeadline"stressbaking (andthe resultinggoodies!)you've beenworking on thisbug for 9 hoursstraight and youdon't even knowwhat you're typinganymoregus isbrokenyour localbuild ishosedSTEAMisbrokensomeonesubmits acode reviewaftermidnightlastminutelabelchangeyou find aregressiona P1investigationcomes inP4goesdownpersonalrecord forworkinbox sizecheatingthesystemwe arelockedoutthis is finedog isspammedin slackthe cafe lineis crazy longand full ofsad-lookingengineersyourcomputerautomaticallyupdatesyour lastminutecheck-infailedprecheckinscrumon FFdayyousubmit arisky CLeclipsecrashesyou'reover-caffeinatedconditionalsign-offyou QA astory < 3hours beforethe FFdeadlineprecheckinbecomesyourcompileryou manageto reproduce arare bug… soit turns out it'sreal... oh noyou realize youwere approachingthis bug all wrongand you've justwasted severalhoursall of usare eatinglunch atour desksan entireteam by us iseating lunchat their desksprecheckintakes >2.5 hoursbug filed pastschemafreeze thatneeds schemachangestresseatinga P1 bugis filed onusanother teamsigned off earlyand is playingping pong veryloudlyyouwhisper“this is fine”to yourselfsomeonesuggests "justcheck it in andgive it a try" onyour story/bugnot being able toexplain to anyoneoutside ofSalesforce what'sgoing on beyondthat it's "a bigdeadline"stressbaking (andthe resultinggoodies!)you've beenworking on thisbug for 9 hoursstraight and youdon't even knowwhat you're typinganymoregus isbrokenyour localbuild ishosedSTEAMisbrokensomeonesubmits acode reviewaftermidnightlastminutelabelchangeyou find aregressiona P1investigationcomes inP4goesdownpersonalrecord forworkinbox sizecheatingthesystemwe arelockedoutthis is finedog isspammedin slackthe cafe lineis crazy longand full ofsad-lookingengineersyourcomputerautomaticallyupdatesyour lastminutecheck-infailedprecheckinscrumon FFdayyousubmit arisky CLeclipsecrashesyou'reover-caffeinatedconditionalsign-offyou QA astory < 3hours beforethe FFdeadlineprecheckinbecomesyourcompileryou manageto reproduce arare bug… soit turns out it'sreal... oh noyou realize youwere approachingthis bug all wrongand you've justwasted severalhoursall of usare eatinglunch atour desksan entireteam by us iseating lunchat their desksprecheckintakes >2.5 hours

Release Freeze Bingo - 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
26
27
28
29
30
31
32
33
34
35
36
  1. bug filed past schema freeze that needs schema change
  2. stress eating
  3. a P1 bug is filed on us
  4. another team signed off early and is playing ping pong very loudly
  5. you whisper “this is fine” to yourself
  6. someone suggests "just check it in and give it a try" on your story/bug
  7. not being able to explain to anyone outside of Salesforce what's going on beyond that it's "a big deadline"
  8. stress baking (and the resulting goodies!)
  9. you've been working on this bug for 9 hours straight and you don't even know what you're typing anymore
  10. gus is broken
  11. your local build is hosed
  12. STEAM is broken
  13. someone submits a code review after midnight
  14. last minute label change
  15. you find a regression
  16. a P1 investigation comes in
  17. P4 goes down
  18. personal record for work inbox size
  19. cheating the system
  20. we are locked out
  21. this is fine dog is spammed in slack
  22. the cafe line is crazy long and full of sad-looking engineers
  23. your computer automatically updates
  24. your last minute check-in failed precheckin
  25. scrum on FF day
  26. you submit a risky CL
  27. eclipse crashes
  28. you're over-caffeinated
  29. conditional sign-off
  30. you QA a story < 3 hours before the FF deadline
  31. precheckin becomes your compiler
  32. you manage to reproduce a rare bug… so it turns out it's real... oh no
  33. you realize you were approaching this bug all wrong and you've just wasted several hours
  34. all of us are eating lunch at our desks
  35. an entire team by us is eating lunch at their desks
  36. precheckin takes > 2.5 hours