Weeffectivelymadeadjustmentsas neededWe werefocusedon thesprint goalWe need torethinkexistingways ofworkingI feeloverwhelmedThere werebottlenecksthat slowedus downWe co-createdacceptancecriteriaWeovercommittedWe have acontinuouslearningcultureWe are ableto learn frommistakes orfailureWe under-estimatedstoriesWe hadeverythingwe neededto meet ourgoalsWe forgot toupdatetechnical/designdocumentationPrioritieswereclearOur workenvironmentischallengingWe brokeanothersquad'scodeI feelvaluedThere wasclear storyscope beforewe added workto the sprintWe collaboratewellasynchronouslyToo manydistractionsAnothersquadbroke ourcodeSub-taskingwashelpfulThere wasgoodparticipationin squadmeetingsToo manynon-valuablemeetingsWeunderstoodthe value ofthe userstoriesMobbingwaseffectiveWesacrificedquality tomeetdeadlinesThe dailyscrumevent wasvaluableJointrefinementswerevaluableThe POprovidedsolidacceptancecriteriaWe haddifficultycoordinatingWeeffectivelymadeadjustmentsas neededWe werefocusedon thesprint goalWe need torethinkexistingways ofworkingI feeloverwhelmedThere werebottlenecksthat slowedus downWe co-createdacceptancecriteriaWeovercommittedWe have acontinuouslearningcultureWe are ableto learn frommistakes orfailureWe under-estimatedstoriesWe hadeverythingwe neededto meet ourgoalsWe forgot toupdatetechnical/designdocumentationPrioritieswereclearOur workenvironmentischallengingWe brokeanothersquad'scodeI feelvaluedThere wasclear storyscope beforewe added workto the sprintWe collaboratewellasynchronouslyToo manydistractionsAnothersquadbroke ourcodeSub-taskingwashelpfulThere wasgoodparticipationin squadmeetingsToo manynon-valuablemeetingsWeunderstoodthe value ofthe userstoriesMobbingwaseffectiveWesacrificedquality tomeetdeadlinesThe dailyscrumevent wasvaluableJointrefinementswerevaluableThe POprovidedsolidacceptancecriteriaWe haddifficultycoordinating

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