P4goesdownyouwhisper“this is fine”to yourselfan entireteam by us iseating lunchat their deskslastminutelabelchangeSTEAMisbrokenstressbaking (andthe resultinggoodies!)scrumon FFdayprecheckintakes >2.5 hoursyour lastminutecheck-infailedprecheckinyou'reover-caffeinateda P1investigationcomes inwe arelockedoutyou find aregressionyou realize youwere approachingthis bug all wrongand you've justwasted severalhoursyou manageto reproduce arare bug… soit turns out it'sreal... oh nopersonalrecord forworkinbox sizeyousubmit arisky CLsomeonesubmits acode reviewaftermidnightthe cafe lineis crazy longand full ofsad-lookingengineersnot being able toexplain to anyoneoutside ofSalesforce what'sgoing on beyondthat it's "a bigdeadline"another teamsigned off earlyand is playingping pong veryloudlyall of usare eatinglunch atour desksgus isbrokenyourcomputerautomaticallyupdateseclipsecrashesyou've beenworking on thisbug for 9 hoursstraight and youdon't even knowwhat you're typinganymorecheatingthesystemyour localbuild ishosedprecheckinbecomesyourcompilersomeonesuggests "justcheck it in andgive it a try" onyour story/bugyou QA astory < 3hours beforethe FFdeadlinea P1 bugis filed onusconditionalsign-offbug filed pastschemafreeze thatneeds schemachangethis is finedog isspammedin slackstresseatingP4goesdownyouwhisper“this is fine”to yourselfan entireteam by us iseating lunchat their deskslastminutelabelchangeSTEAMisbrokenstressbaking (andthe resultinggoodies!)scrumon FFdayprecheckintakes >2.5 hoursyour lastminutecheck-infailedprecheckinyou'reover-caffeinateda P1investigationcomes inwe arelockedoutyou find aregressionyou realize youwere approachingthis bug all wrongand you've justwasted severalhoursyou manageto reproduce arare bug… soit turns out it'sreal... oh nopersonalrecord forworkinbox sizeyousubmit arisky CLsomeonesubmits acode reviewaftermidnightthe cafe lineis crazy longand full ofsad-lookingengineersnot being able toexplain to anyoneoutside ofSalesforce what'sgoing on beyondthat it's "a bigdeadline"another teamsigned off earlyand is playingping pong veryloudlyall of usare eatinglunch atour desksgus isbrokenyourcomputerautomaticallyupdateseclipsecrashesyou've beenworking on thisbug for 9 hoursstraight and youdon't even knowwhat you're typinganymorecheatingthesystemyour localbuild ishosedprecheckinbecomesyourcompilersomeonesuggests "justcheck it in andgive it a try" onyour story/bugyou QA astory < 3hours beforethe FFdeadlinea P1 bugis filed onusconditionalsign-offbug filed pastschemafreeze thatneeds schemachangethis is finedog isspammedin slackstresseating

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