lastminutelabelchangeyou'reover-caffeinatedyouwhisper“this is fine”to yourselfwe arelockedoutnot being able toexplain to anyoneoutside ofSalesforce what'sgoing on beyondthat it's "a bigdeadline"precheckinbecomesyourcompileryousubmit arisky CLgus isbrokenanother teamsigned off earlyand is playingping pong veryloudlystressbaking (andthe resultinggoodies!)this is finedog isspammedin slackSTEAMisbrokenyou've beenworking on thisbug for 9 hoursstraight and youdon't even knowwhat you're typinganymoreall of usare eatinglunch atour deskspersonalrecord forworkinbox sizeyour lastminutecheck-infailedprecheckinbug filed pastschemafreeze thatneeds schemachangesomeonesubmits acode reviewaftermidnightprecheckintakes >2.5 hoursscrumon FFdayyou find aregressionP4goesdowna P1 bugis filed onuseclipsecrashesthe cafe lineis crazy longand full ofsad-lookingengineersyou QA astory < 3hours beforethe FFdeadlinestresseatingyour localbuild ishosedan entireteam by us iseating lunchat their desksyourcomputerautomaticallyupdatescheatingthesystemyou realize youwere approachingthis bug all wrongand you've justwasted severalhoursyou manageto reproduce arare bug… soit turns out it'sreal... oh noconditionalsign-offa P1investigationcomes insomeonesuggests "justcheck it in andgive it a try" onyour story/buglastminutelabelchangeyou'reover-caffeinatedyouwhisper“this is fine”to yourselfwe arelockedoutnot being able toexplain to anyoneoutside ofSalesforce what'sgoing on beyondthat it's "a bigdeadline"precheckinbecomesyourcompileryousubmit arisky CLgus isbrokenanother teamsigned off earlyand is playingping pong veryloudlystressbaking (andthe resultinggoodies!)this is finedog isspammedin slackSTEAMisbrokenyou've beenworking on thisbug for 9 hoursstraight and youdon't even knowwhat you're typinganymoreall of usare eatinglunch atour deskspersonalrecord forworkinbox sizeyour lastminutecheck-infailedprecheckinbug filed pastschemafreeze thatneeds schemachangesomeonesubmits acode reviewaftermidnightprecheckintakes >2.5 hoursscrumon FFdayyou find aregressionP4goesdowna P1 bugis filed onuseclipsecrashesthe cafe lineis crazy longand full ofsad-lookingengineersyou QA astory < 3hours beforethe FFdeadlinestresseatingyour localbuild ishosedan entireteam by us iseating lunchat their desksyourcomputerautomaticallyupdatescheatingthesystemyou realize youwere approachingthis bug all wrongand you've justwasted severalhoursyou manageto reproduce arare bug… soit turns out it'sreal... oh noconditionalsign-offa P1investigationcomes insomeonesuggests "justcheck it in andgive it a try" onyour story/bug

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