this is finedog isspammedin slackpersonalrecord forworkinbox sizenot being able toexplain to anyoneoutside ofSalesforce what'sgoing on beyondthat it's "a bigdeadline"lastminutelabelchangeyou manageto reproduce arare bug… soit turns out it'sreal... oh noprecheckintakes >2.5 hoursall of usare eatinglunch atour desksa P1 bugis filed onusgus isbrokenconditionalsign-offyouwhisper“this is fine”to yourselfP4goesdownscrumon FFdayyou find aregressionyou'reover-caffeinatedyour localbuild ishosedwe arelockedoutyou realize youwere approachingthis bug all wrongand you've justwasted severalhoursthe cafe lineis crazy longand full ofsad-lookingengineersstresseatingprecheckinbecomesyourcompilercheatingthesystemyou QA astory < 3hours beforethe FFdeadlinebug filed pastschemafreeze thatneeds schemachangeSTEAMisbrokenan entireteam by us iseating lunchat their desksyousubmit arisky CLsomeonesuggests "justcheck it in andgive it a try" onyour story/bugyourcomputerautomaticallyupdateseclipsecrashesyou've beenworking on thisbug for 9 hoursstraight and youdon't even knowwhat you're typinganymoreanother teamsigned off earlyand is playingping pong veryloudlyyour lastminutecheck-infailedprecheckinsomeonesubmits acode reviewaftermidnightstressbaking (andthe resultinggoodies!)a P1investigationcomes inthis is finedog isspammedin slackpersonalrecord forworkinbox sizenot being able toexplain to anyoneoutside ofSalesforce what'sgoing on beyondthat it's "a bigdeadline"lastminutelabelchangeyou manageto reproduce arare bug… soit turns out it'sreal... oh noprecheckintakes >2.5 hoursall of usare eatinglunch atour desksa P1 bugis filed onusgus isbrokenconditionalsign-offyouwhisper“this is fine”to yourselfP4goesdownscrumon FFdayyou find aregressionyou'reover-caffeinatedyour localbuild ishosedwe arelockedoutyou realize youwere approachingthis bug all wrongand you've justwasted severalhoursthe cafe lineis crazy longand full ofsad-lookingengineersstresseatingprecheckinbecomesyourcompilercheatingthesystemyou QA astory < 3hours beforethe FFdeadlinebug filed pastschemafreeze thatneeds schemachangeSTEAMisbrokenan entireteam by us iseating lunchat their desksyousubmit arisky CLsomeonesuggests "justcheck it in andgive it a try" onyour story/bugyourcomputerautomaticallyupdateseclipsecrashesyou've beenworking on thisbug for 9 hoursstraight and youdon't even knowwhat you're typinganymoreanother teamsigned off earlyand is playingping pong veryloudlyyour lastminutecheck-infailedprecheckinsomeonesubmits acode reviewaftermidnightstressbaking (andthe resultinggoodies!)a P1investigationcomes in

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