Our workenvironmentischallengingSub-taskingwashelpfulWe are ableto learn frommistakes orfailureThere wasgoodparticipationin squadmeetingsWe hadeverythingwe neededto meet ourgoalsJointrefinementswerevaluableWe werefocusedon thesprint goalWe forgot toupdatetechnical/designdocumentationMobbingwaseffectiveAnothersquadbroke ourcodeThe dailyscrumevent wasvaluableWeovercommittedI feeloverwhelmedToo manynon-valuablemeetingsWe co-createdacceptancecriteriaWeunderstoodthe value ofthe userstoriesWesacrificedquality tomeetdeadlinesWe brokeanothersquad'scodeWe haddifficultycoordinatingPrioritieswereclearWe have acontinuouslearningcultureThere werebottlenecksthat slowedus downI feelvaluedWe collaboratewellasynchronouslyThe POprovidedsolidacceptancecriteriaWeeffectivelymadeadjustmentsas neededThere wasclear storyscope beforewe added workto the sprintToo manydistractionsWe need torethinkexistingways ofworkingWe under-estimatedstoriesOur workenvironmentischallengingSub-taskingwashelpfulWe are ableto learn frommistakes orfailureThere wasgoodparticipationin squadmeetingsWe hadeverythingwe neededto meet ourgoalsJointrefinementswerevaluableWe werefocusedon thesprint goalWe forgot toupdatetechnical/designdocumentationMobbingwaseffectiveAnothersquadbroke ourcodeThe dailyscrumevent wasvaluableWeovercommittedI feeloverwhelmedToo manynon-valuablemeetingsWe co-createdacceptancecriteriaWeunderstoodthe value ofthe userstoriesWesacrificedquality tomeetdeadlinesWe brokeanothersquad'scodeWe haddifficultycoordinatingPrioritieswereclearWe have acontinuouslearningcultureThere werebottlenecksthat slowedus downI feelvaluedWe collaboratewellasynchronouslyThe POprovidedsolidacceptancecriteriaWeeffectivelymadeadjustmentsas neededThere wasclear storyscope beforewe added workto the sprintToo manydistractionsWe need torethinkexistingways ofworkingWe under-estimatedstories

2403-1 Retro Bingo Emerald - 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
  1. Our work environment is challenging
  2. Sub-tasking was helpful
  3. We are able to learn from mistakes or failure
  4. There was good participation in squad meetings
  5. We had everything we needed to meet our goals
  6. Joint refinements were valuable
  7. We were focused on the sprint goal
  8. We forgot to update technical/design documentation
  9. Mobbing was effective
  10. Another squad broke our code
  11. The daily scrum event was valuable
  12. We overcommitted
  13. I feel overwhelmed
  14. Too many non-valuable meetings
  15. We co-created acceptance criteria
  16. We understood the value of the user stories
  17. We sacrificed quality to meet deadlines
  18. We broke another squad's code
  19. We had difficulty coordinating
  20. Priorities were clear
  21. We have a continuous learning culture
  22. There were bottlenecks that slowed us down
  23. I feel valued
  24. We collaborate well asynchronously
  25. The PO provided solid acceptance criteria
  26. We effectively made adjustments as needed
  27. There was clear story scope before we added work to the sprint
  28. Too many distractions
  29. We need to rethink existing ways of working
  30. We under -estimated stories