IgnoreproblemsBusinessexpectationsare clearTalkingtoomuchEffectiveestimationLearningculture isrespectedProblemSolving inDailyScrumBusinessis opento ideasForgettingTools/DocumentsChallengingworkenvironmentKnowingDefinitionof DoneSprintgoalshould bein placeFamiliarwith theroadmapClarity incommunicationin ADONeed torethinkfew waysof workingNotpayingattentionNotspeakingupTicketsleft onboard toolongStretchinggoals tothe sprintDifficulty incoordinationPlanningeveryiterationCompromise ofquality due toimposeddeadlines,scope andresourcesTickets haveenoughdetail tocommitOvercommittingorunderestimatingTestingleft to theend of thesprintIgnoreproblemsBusinessexpectationsare clearTalkingtoomuchEffectiveestimationLearningculture isrespectedProblemSolving inDailyScrumBusinessis opento ideasForgettingTools/DocumentsChallengingworkenvironmentKnowingDefinitionof DoneSprintgoalshould bein placeFamiliarwith theroadmapClarity incommunicationin ADONeed torethinkfew waysof workingNotpayingattentionNotspeakingupTicketsleft onboard toolongStretchinggoals tothe sprintDifficulty incoordinationPlanningeveryiterationCompromise ofquality due toimposeddeadlines,scope andresourcesTickets haveenoughdetail tocommitOvercommittingorunderestimatingTestingleft to theend of thesprint

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