Compromise ofquality due toimposeddeadlines,scope andresourcesIgnoreproblemsNotpayingattentionTicketsleft onboard toolongLearningculture isrespectedTestingleft to theend of thesprintTalkingtoomuchDifficulty incoordinationNotspeakingupFamiliarwith theroadmapClarity incommunicationin ADOBusinessis opento ideasKnowingDefinitionof DoneProblemSolving inDailyScrumTickets haveenoughdetail tocommitChallengingworkenvironmentPlanningeveryiterationStretchinggoals tothe sprintNeed torethinkfew waysof workingForgettingTools/DocumentsBusinessexpectationsare clearEffectiveestimationSprintgoalshould bein placeOvercommittingorunderestimatingCompromise ofquality due toimposeddeadlines,scope andresourcesIgnoreproblemsNotpayingattentionTicketsleft onboard toolongLearningculture isrespectedTestingleft to theend of thesprintTalkingtoomuchDifficulty incoordinationNotspeakingupFamiliarwith theroadmapClarity incommunicationin ADOBusinessis opento ideasKnowingDefinitionof DoneProblemSolving inDailyScrumTickets haveenoughdetail tocommitChallengingworkenvironmentPlanningeveryiterationStretchinggoals tothe sprintNeed torethinkfew waysof workingForgettingTools/DocumentsBusinessexpectationsare clearEffectiveestimationSprintgoalshould bein placeOvercommittingorunderestimating

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