KnowingDefinitionof DoneOvercommittingorunderestimatingNeed torethinkfew waysof workingTalkingtoomuchTestingleft to theend of thesprintSprintgoalshould bein placeIgnoreproblemsStretchinggoals tothe sprintDifficulty incoordinationLearningculture isrespectedPlanningeveryiterationForgettingTools/DocumentsTickets haveenoughdetail tocommitProblemSolving inDailyScrumChallengingworkenvironmentNotpayingattentionBusinessexpectationsare clearClarity incommunicationin ADOTicketsleft onboard toolongCompromise ofquality due toimposeddeadlines,scope andresourcesNotspeakingupFamiliarwith theroadmapEffectiveestimationBusinessis opento ideasKnowingDefinitionof DoneOvercommittingorunderestimatingNeed torethinkfew waysof workingTalkingtoomuchTestingleft to theend of thesprintSprintgoalshould bein placeIgnoreproblemsStretchinggoals tothe sprintDifficulty incoordinationLearningculture isrespectedPlanningeveryiterationForgettingTools/DocumentsTickets haveenoughdetail tocommitProblemSolving inDailyScrumChallengingworkenvironmentNotpayingattentionBusinessexpectationsare clearClarity incommunicationin ADOTicketsleft onboard toolongCompromise ofquality due toimposeddeadlines,scope andresourcesNotspeakingupFamiliarwith theroadmapEffectiveestimationBusinessis opento ideas

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