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