your localbuild ishosedscrumon FFdaypersonalrecord forworkinbox sizeyou'reover-caffeinateda P1investigationcomes inbug filed pastschemafreeze thatneeds schemachangeSTEAMisbrokenstressbaking (andthe resultinggoodies!)P4goesdownyouwhisper“this is fine”to yourselfyou manageto reproduce arare bug… soit turns out it'sreal... oh noa P1 bugis filed onusyou find aregressionnot being able toexplain to anyoneoutside ofSalesforce what'sgoing on beyondthat it's "a bigdeadline"precheckinbecomesyourcompilerprecheckintakes >2.5 hourssomeonesuggests "justcheck it in andgive it a try" onyour story/bugyousubmit arisky CLconditionalsign-offcheatingthesystemyou QA astory < 3hours beforethe FFdeadlineyour lastminutecheck-infailedprecheckinyourcomputerautomaticallyupdatesall of usare eatinglunch atour deskslastminutelabelchangeeclipsecrashessomeonesubmits acode reviewaftermidnightgus isbrokenstresseatingthe cafe lineis crazy longand full ofsad-lookingengineersan entireteam by us iseating lunchat their desksyou realize youwere approachingthis bug all wrongand you've justwasted severalhourswe arelockedoutthis is finedog isspammedin slackanother teamsigned off earlyand is playingping pong veryloudlyyou've beenworking on thisbug for 9 hoursstraight and youdon't even knowwhat you're typinganymoreyour localbuild ishosedscrumon FFdaypersonalrecord forworkinbox sizeyou'reover-caffeinateda P1investigationcomes inbug filed pastschemafreeze thatneeds schemachangeSTEAMisbrokenstressbaking (andthe resultinggoodies!)P4goesdownyouwhisper“this is fine”to yourselfyou manageto reproduce arare bug… soit turns out it'sreal... oh noa P1 bugis filed onusyou find aregressionnot being able toexplain to anyoneoutside ofSalesforce what'sgoing on beyondthat it's "a bigdeadline"precheckinbecomesyourcompilerprecheckintakes >2.5 hourssomeonesuggests "justcheck it in andgive it a try" onyour story/bugyousubmit arisky CLconditionalsign-offcheatingthesystemyou QA astory < 3hours beforethe FFdeadlineyour lastminutecheck-infailedprecheckinyourcomputerautomaticallyupdatesall of usare eatinglunch atour deskslastminutelabelchangeeclipsecrashessomeonesubmits acode reviewaftermidnightgus isbrokenstresseatingthe cafe lineis crazy longand full ofsad-lookingengineersan entireteam by us iseating lunchat their desksyou realize youwere approachingthis bug all wrongand you've justwasted severalhourswe arelockedoutthis is finedog isspammedin slackanother teamsigned off earlyand is playingping pong veryloudlyyou've beenworking on thisbug for 9 hoursstraight and youdon't even knowwhat you're typinganymore

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