Anothersquadbroke ourcodeWe brokeanothersquad'scodeWe hadeverythingwe neededto meet ourgoalsThere wasclear storyscope beforewe added workto the sprintThe dailyscrumevent wasvaluableWeeffectivelymadeadjustmentsas neededOur workenvironmentischallengingWe collaboratewellasynchronouslyThere wasgoodparticipationin squadmeetingsWeovercommittedThere werebottlenecksthat slowedus downWesacrificedquality tomeetdeadlinesWe forgot toupdatetechnical/designdocumentationThe POprovidedsolidacceptancecriteriaJointrefinementswerevaluableToo manynon-valuablemeetingsSub-taskingwashelpfulWe co-createdacceptancecriteriaMobbingwaseffectiveToo manydistractionsI feelvaluedWe werefocusedon thesprint goalWe haddifficultycoordinatingWe under-estimatedstoriesI feeloverwhelmedWe have acontinuouslearningcultureWe need torethinkexistingways ofworkingWeunderstoodthe value ofthe userstoriesPrioritieswereclearWe are ableto learn frommistakes orfailureAnothersquadbroke ourcodeWe brokeanothersquad'scodeWe hadeverythingwe neededto meet ourgoalsThere wasclear storyscope beforewe added workto the sprintThe dailyscrumevent wasvaluableWeeffectivelymadeadjustmentsas neededOur workenvironmentischallengingWe collaboratewellasynchronouslyThere wasgoodparticipationin squadmeetingsWeovercommittedThere werebottlenecksthat slowedus downWesacrificedquality tomeetdeadlinesWe forgot toupdatetechnical/designdocumentationThe POprovidedsolidacceptancecriteriaJointrefinementswerevaluableToo manynon-valuablemeetingsSub-taskingwashelpfulWe co-createdacceptancecriteriaMobbingwaseffectiveToo manydistractionsI feelvaluedWe werefocusedon thesprint goalWe haddifficultycoordinatingWe under-estimatedstoriesI feeloverwhelmedWe have acontinuouslearningcultureWe need torethinkexistingways ofworkingWeunderstoodthe value ofthe userstoriesPrioritieswereclearWe are ableto learn frommistakes orfailure

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