you'reover-caffeinatedyou've beenworking on thisbug for 9 hoursstraight and youdon't even knowwhat you're typinganymorea P1investigationcomes ingus isbrokenwe arelockedoutthe cafe lineis crazy longand full ofsad-lookingengineersnot being able toexplain to anyoneoutside ofSalesforce what'sgoing on beyondthat it's "a bigdeadline"stresseatingbug filed pastschemafreeze thatneeds schemachangelastminutelabelchangeprecheckintakes >2.5 hoursconditionalsign-offall of usare eatinglunch atour desksthis is finedog isspammedin slackscrumon FFdaycheatingthesystemyou realize youwere approachingthis bug all wrongand you've justwasted severalhoursyousubmit arisky CLa P1 bugis filed onusanother teamsigned off earlyand is playingping pong veryloudlyan entireteam by us iseating lunchat their desksyou manageto reproduce arare bug… soit turns out it'sreal... oh noyourcomputerautomaticallyupdatesP4goesdownprecheckinbecomesyourcompilerSTEAMisbrokenstressbaking (andthe resultinggoodies!)someonesuggests "justcheck it in andgive it a try" onyour story/bugeclipsecrashesyour localbuild ishosedsomeonesubmits acode reviewaftermidnightyou find aregressionyour lastminutecheck-infailedprecheckinpersonalrecord forworkinbox sizeyou QA astory < 3hours beforethe FFdeadlineyouwhisper“this is fine”to yourselfyou'reover-caffeinatedyou've beenworking on thisbug for 9 hoursstraight and youdon't even knowwhat you're typinganymorea P1investigationcomes ingus isbrokenwe arelockedoutthe cafe lineis crazy longand full ofsad-lookingengineersnot being able toexplain to anyoneoutside ofSalesforce what'sgoing on beyondthat it's "a bigdeadline"stresseatingbug filed pastschemafreeze thatneeds schemachangelastminutelabelchangeprecheckintakes >2.5 hoursconditionalsign-offall of usare eatinglunch atour desksthis is finedog isspammedin slackscrumon FFdaycheatingthesystemyou realize youwere approachingthis bug all wrongand you've justwasted severalhoursyousubmit arisky CLa P1 bugis filed onusanother teamsigned off earlyand is playingping pong veryloudlyan entireteam by us iseating lunchat their desksyou manageto reproduce arare bug… soit turns out it'sreal... oh noyourcomputerautomaticallyupdatesP4goesdownprecheckinbecomesyourcompilerSTEAMisbrokenstressbaking (andthe resultinggoodies!)someonesuggests "justcheck it in andgive it a try" onyour story/bugeclipsecrashesyour localbuild ishosedsomeonesubmits acode reviewaftermidnightyou find aregressionyour lastminutecheck-infailedprecheckinpersonalrecord forworkinbox sizeyou QA astory < 3hours beforethe FFdeadlineyouwhisper“this is fine”to yourself

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