NotpayingattentionChallengingworkenvironmentLearningculture isrespectedForgettingTools/DocumentsDifficulty incoordinationBusinessexpectationsare clearOvercommittingorunderestimatingClarity incommunicationin ADOStretchinggoals tothe sprintProblemSolving inDailyScrumEffectiveestimationFamiliarwith theroadmapTalkingtoomuchCompromise ofquality due toimposeddeadlines,scope andresourcesPlanningeveryiterationKnowingDefinitionof DoneTicketsleft onboard toolongTestingleft to theend of thesprintTickets haveenoughdetail tocommitNeed torethinkfew waysof workingBusinessis opento ideasSprintgoalshould bein placeNotspeakingupIgnoreproblemsNotpayingattentionChallengingworkenvironmentLearningculture isrespectedForgettingTools/DocumentsDifficulty incoordinationBusinessexpectationsare clearOvercommittingorunderestimatingClarity incommunicationin ADOStretchinggoals tothe sprintProblemSolving inDailyScrumEffectiveestimationFamiliarwith theroadmapTalkingtoomuchCompromise ofquality due toimposeddeadlines,scope andresourcesPlanningeveryiterationKnowingDefinitionof DoneTicketsleft onboard toolongTestingleft to theend of thesprintTickets haveenoughdetail tocommitNeed torethinkfew waysof workingBusinessis opento ideasSprintgoalshould bein placeNotspeakingupIgnoreproblems

Retrospective 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
  1. Not paying attention
  2. Challenging work environment
  3. Learning culture is respected
  4. Forgetting Tools/ Documents
  5. Difficulty in coordination
  6. Business expectations are clear
  7. Overcommitting or underestimating
  8. Clarity in communication in ADO
  9. Stretching goals to the sprint
  10. Problem Solving in Daily Scrum
  11. Effective estimation
  12. Familiar with the roadmap
  13. Talking too much
  14. Compromise of quality due to imposed deadlines, scope and resources
  15. Planning every iteration
  16. Knowing Definition of Done
  17. Tickets left on board too long
  18. Testing left to the end of the sprint
  19. Tickets have enough detail to commit
  20. Need to rethink few ways of working
  21. Business is open to ideas
  22. Sprint goal should be in place
  23. Not speaking up
  24. Ignore problems