this is finedog isspammedin slackstresseatinga P1investigationcomes ingus isbrokenyou'reover-caffeinatedscrumon FFdayconditionalsign-offprecheckinbecomesyourcompilerthe cafe lineis crazy longand full ofsad-lookingengineersstressbaking (andthe resultinggoodies!)all of usare eatinglunch atour desksnot being able toexplain to anyoneoutside ofSalesforce what'sgoing on beyondthat it's "a bigdeadline"yourcomputerautomaticallyupdatesyour localbuild ishosedP4goesdownlastminutelabelchangewe arelockedoutpersonalrecord forworkinbox sizea P1 bugis filed onusyou realize youwere approachingthis bug all wrongand you've justwasted severalhoursanother teamsigned off earlyand is playingping pong veryloudlyeclipsecrashessomeonesuggests "justcheck it in andgive it a try" onyour story/bugSTEAMisbrokencheatingthesystemyousubmit arisky CLyou QA astory < 3hours beforethe FFdeadlineyou'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 noan entireteam by us iseating lunchat their desksyou find aregressionsomeonesubmits acode reviewaftermidnightprecheckintakes >2.5 hoursyour lastminutecheck-infailedprecheckinbug filed pastschemafreeze thatneeds schemachangeyouwhisper“this is fine”to yourselfthis is finedog isspammedin slackstresseatinga P1investigationcomes ingus isbrokenyou'reover-caffeinatedscrumon FFdayconditionalsign-offprecheckinbecomesyourcompilerthe cafe lineis crazy longand full ofsad-lookingengineersstressbaking (andthe resultinggoodies!)all of usare eatinglunch atour desksnot being able toexplain to anyoneoutside ofSalesforce what'sgoing on beyondthat it's "a bigdeadline"yourcomputerautomaticallyupdatesyour localbuild ishosedP4goesdownlastminutelabelchangewe arelockedoutpersonalrecord forworkinbox sizea P1 bugis filed onusyou realize youwere approachingthis bug all wrongand you've justwasted severalhoursanother teamsigned off earlyand is playingping pong veryloudlyeclipsecrashessomeonesuggests "justcheck it in andgive it a try" onyour story/bugSTEAMisbrokencheatingthesystemyousubmit arisky CLyou QA astory < 3hours beforethe FFdeadlineyou'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 noan entireteam by us iseating lunchat their desksyou find aregressionsomeonesubmits acode reviewaftermidnightprecheckintakes >2.5 hoursyour lastminutecheck-infailedprecheckinbug filed pastschemafreeze thatneeds schemachangeyouwhisper“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. this is fine dog is spammed in slack
  2. stress eating
  3. a P1 investigation comes in
  4. gus is broken
  5. you're over-caffeinated
  6. scrum on FF day
  7. conditional sign-off
  8. precheckin becomes your compiler
  9. the cafe line is crazy long and full of sad-looking engineers
  10. stress baking (and the resulting goodies!)
  11. all of us are eating lunch at our desks
  12. not being able to explain to anyone outside of Salesforce what's going on beyond that it's "a big deadline"
  13. your computer automatically updates
  14. your local build is hosed
  15. P4 goes down
  16. last minute label change
  17. we are locked out
  18. personal record for work inbox size
  19. a P1 bug is filed on us
  20. you realize you were approaching this bug all wrong and you've just wasted several hours
  21. another team signed off early and is playing ping pong very loudly
  22. eclipse crashes
  23. someone suggests "just check it in and give it a try" on your story/bug
  24. STEAM is broken
  25. cheating the system
  26. you submit a risky CL
  27. you QA a story < 3 hours before the FF deadline
  28. you've been working on this bug for 9 hours straight and you don't even know what you're typing anymore
  29. you manage to reproduce a rare bug… so it turns out it's real... oh no
  30. an entire team by us is eating lunch at their desks
  31. you find a regression
  32. someone submits a code review after midnight
  33. precheckin takes > 2.5 hours
  34. your last minute check-in failed precheckin
  35. bug filed past schema freeze that needs schema change
  36. you whisper “this is fine” to yourself