There werebottlenecksthat slowedus downToo manynon-valuablemeetingsToo manydistractionsThere wasclear storyscope beforewe added workto the sprintSub-taskingwashelpfulWe need torethinkexistingways ofworkingWe collaboratewellasynchronouslyWe brokeanothersquad'scodeThere wasgoodparticipationin squadmeetingsWe werefocusedon thesprint goalPrioritieswereclearThe POprovidedsolidacceptancecriteriaWe have acontinuouslearningcultureWeeffectivelymadeadjustmentsas neededWeunderstoodthe value ofthe userstoriesOur workenvironmentischallengingThe dailyscrumevent wasvaluableWe are ableto learn frommistakes orfailureWesacrificedquality tomeetdeadlinesMobbingwaseffectiveWe haddifficultycoordinatingWe under-estimatedstoriesI feelvaluedWe hadeverythingwe neededto meet ourgoalsI feeloverwhelmedWe forgot toupdatetechnical/designdocumentationWeovercommittedAnothersquadbroke ourcodeWe co-createdacceptancecriteriaJointrefinementswerevaluableThere werebottlenecksthat slowedus downToo manynon-valuablemeetingsToo manydistractionsThere wasclear storyscope beforewe added workto the sprintSub-taskingwashelpfulWe need torethinkexistingways ofworkingWe collaboratewellasynchronouslyWe brokeanothersquad'scodeThere wasgoodparticipationin squadmeetingsWe werefocusedon thesprint goalPrioritieswereclearThe POprovidedsolidacceptancecriteriaWe have acontinuouslearningcultureWeeffectivelymadeadjustmentsas neededWeunderstoodthe value ofthe userstoriesOur workenvironmentischallengingThe dailyscrumevent wasvaluableWe are ableto learn frommistakes orfailureWesacrificedquality tomeetdeadlinesMobbingwaseffectiveWe haddifficultycoordinatingWe under-estimatedstoriesI feelvaluedWe hadeverythingwe neededto meet ourgoalsI feeloverwhelmedWe forgot toupdatetechnical/designdocumentationWeovercommittedAnothersquadbroke ourcodeWe co-createdacceptancecriteriaJointrefinementswerevaluable

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