KnowingDefinitionof DoneFamiliarwith theroadmapIgnoreproblemsClarity incommunicationin ADOOvercommittingorunderestimatingTicketsleft onboard toolongPlanningeveryiterationTickets haveenoughdetail tocommitLearningculture isrespectedNeed torethinkfew waysof workingNotspeakingupEffectiveestimationStretchinggoals tothe sprintTestingleft to theend of thesprintNotpayingattentionTalkingtoomuchCompromise ofquality due toimposeddeadlines,scope andresourcesBusinessexpectationsare clearProblemSolving inDailyScrumForgettingTools/DocumentsSprintgoalshould bein placeChallengingworkenvironmentBusinessis opento ideasDifficulty incoordinationKnowingDefinitionof DoneFamiliarwith theroadmapIgnoreproblemsClarity incommunicationin ADOOvercommittingorunderestimatingTicketsleft onboard toolongPlanningeveryiterationTickets haveenoughdetail tocommitLearningculture isrespectedNeed torethinkfew waysof workingNotspeakingupEffectiveestimationStretchinggoals tothe sprintTestingleft to theend of thesprintNotpayingattentionTalkingtoomuchCompromise ofquality due toimposeddeadlines,scope andresourcesBusinessexpectationsare clearProblemSolving inDailyScrumForgettingTools/DocumentsSprintgoalshould bein placeChallengingworkenvironmentBusinessis opento ideasDifficulty incoordination

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