stressbaking (andthe resultinggoodies!)your lastminutecheck-infailedprecheckinyou QA astory < 3hours beforethe FFdeadlineconditionalsign-offprecheckintakes >2.5 hoursprecheckinbecomesyourcompilerall of usare eatinglunch atour desksyouwhisper“this is fine”to yourselfthe cafe lineis crazy longand full ofsad-lookingengineersa P1investigationcomes ingus isbrokenwe arelockedouteclipsecrashesscrumon FFdaysomeonesubmits acode reviewaftermidnighta P1 bugis filed onusstresseatingyou find aregressionthis is finedog isspammedin slackyou've beenworking on thisbug for 9 hoursstraight and youdon't even knowwhat you're typinganymoreyou manageto reproduce arare bug… soit turns out it'sreal... oh noyou'reover-caffeinatedyour localbuild ishosedP4goesdownsomeonesuggests "justcheck it in andgive it a try" onyour story/buganother teamsigned off earlyand is playingping pong veryloudlyan entireteam by us iseating lunchat their desksyourcomputerautomaticallyupdateslastminutelabelchangeyou realize youwere approachingthis bug all wrongand you've justwasted severalhoursyousubmit arisky CLSTEAMisbrokenbug filed pastschemafreeze thatneeds schemachangepersonalrecord forworkinbox sizenot being able toexplain to anyoneoutside ofSalesforce what'sgoing on beyondthat it's "a bigdeadline"cheatingthesystemstressbaking (andthe resultinggoodies!)your lastminutecheck-infailedprecheckinyou QA astory < 3hours beforethe FFdeadlineconditionalsign-offprecheckintakes >2.5 hoursprecheckinbecomesyourcompilerall of usare eatinglunch atour desksyouwhisper“this is fine”to yourselfthe cafe lineis crazy longand full ofsad-lookingengineersa P1investigationcomes ingus isbrokenwe arelockedouteclipsecrashesscrumon FFdaysomeonesubmits acode reviewaftermidnighta P1 bugis filed onusstresseatingyou find aregressionthis is finedog isspammedin slackyou've beenworking on thisbug for 9 hoursstraight and youdon't even knowwhat you're typinganymoreyou manageto reproduce arare bug… soit turns out it'sreal... oh noyou'reover-caffeinatedyour localbuild ishosedP4goesdownsomeonesuggests "justcheck it in andgive it a try" onyour story/buganother teamsigned off earlyand is playingping pong veryloudlyan entireteam by us iseating lunchat their desksyourcomputerautomaticallyupdateslastminutelabelchangeyou realize youwere approachingthis bug all wrongand you've justwasted severalhoursyousubmit arisky CLSTEAMisbrokenbug filed pastschemafreeze thatneeds schemachangepersonalrecord forworkinbox sizenot being able toexplain to anyoneoutside ofSalesforce what'sgoing on beyondthat it's "a bigdeadline"cheatingthesystem

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