you QA astory < 3hours beforethe FFdeadlinestressbaking (andthe resultinggoodies!)cheatingthesysteman entireteam by us iseating lunchat their desksthis is finedog isspammedin slackyou'reover-caffeinatedyour lastminutecheck-infailedprecheckinyour localbuild ishosedgus isbrokeneclipsecrasheswe arelockedoutprecheckintakes >2.5 hoursconditionalsign-offyousubmit arisky CLyourcomputerautomaticallyupdatesyou manageto reproduce arare bug… soit turns out it'sreal... oh nosomeonesubmits acode reviewaftermidnightyou find aregressionlastminutelabelchangeanother teamsigned off earlyand is playingping pong veryloudlya P1investigationcomes instresseatingsomeonesuggests "justcheck it in andgive it a try" onyour story/bugnot being able toexplain to anyoneoutside ofSalesforce what'sgoing on beyondthat it's "a bigdeadline"you've beenworking on thisbug for 9 hoursstraight and youdon't even knowwhat you're typinganymorescrumon FFdayP4goesdownbug filed pastschemafreeze thatneeds schemachangeprecheckinbecomesyourcompilerthe cafe lineis crazy longand full ofsad-lookingengineersSTEAMisbrokenall of usare eatinglunch atour desksyouwhisper“this is fine”to yourselfpersonalrecord forworkinbox sizea P1 bugis filed onusyou realize youwere approachingthis bug all wrongand you've justwasted severalhoursyou QA astory < 3hours beforethe FFdeadlinestressbaking (andthe resultinggoodies!)cheatingthesysteman entireteam by us iseating lunchat their desksthis is finedog isspammedin slackyou'reover-caffeinatedyour lastminutecheck-infailedprecheckinyour localbuild ishosedgus isbrokeneclipsecrasheswe arelockedoutprecheckintakes >2.5 hoursconditionalsign-offyousubmit arisky CLyourcomputerautomaticallyupdatesyou manageto reproduce arare bug… soit turns out it'sreal... oh nosomeonesubmits acode reviewaftermidnightyou find aregressionlastminutelabelchangeanother teamsigned off earlyand is playingping pong veryloudlya P1investigationcomes instresseatingsomeonesuggests "justcheck it in andgive it a try" onyour story/bugnot being able toexplain to anyoneoutside ofSalesforce what'sgoing on beyondthat it's "a bigdeadline"you've beenworking on thisbug for 9 hoursstraight and youdon't even knowwhat you're typinganymorescrumon FFdayP4goesdownbug filed pastschemafreeze thatneeds schemachangeprecheckinbecomesyourcompilerthe cafe lineis crazy longand full ofsad-lookingengineersSTEAMisbrokenall of usare eatinglunch atour desksyouwhisper“this is fine”to yourselfpersonalrecord forworkinbox sizea P1 bugis filed onusyou realize youwere approachingthis bug all wrongand you've justwasted severalhours

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