Sprintgoalshould bein placeOvercommittingorunderestimatingTalkingtoomuchNotpayingattentionEffectiveestimationNeed torethinkfew waysof workingDifficulty incoordinationForgettingTools/DocumentsLearningculture isrespectedTicketsleft onboard toolongCompromise ofquality due toimposeddeadlines,scope andresourcesTickets haveenoughdetail tocommitClarity incommunicationin ADOProblemSolving inDailyScrumFamiliarwith theroadmapPlanningeveryiterationStretchinggoals tothe sprintIgnoreproblemsTestingleft to theend of thesprintChallengingworkenvironmentNotspeakingupKnowingDefinitionof DoneBusinessis opento ideasBusinessexpectationsare clearSprintgoalshould bein placeOvercommittingorunderestimatingTalkingtoomuchNotpayingattentionEffectiveestimationNeed torethinkfew waysof workingDifficulty incoordinationForgettingTools/DocumentsLearningculture isrespectedTicketsleft onboard toolongCompromise ofquality due toimposeddeadlines,scope andresourcesTickets haveenoughdetail tocommitClarity incommunicationin ADOProblemSolving inDailyScrumFamiliarwith theroadmapPlanningeveryiterationStretchinggoals tothe sprintIgnoreproblemsTestingleft to theend of thesprintChallengingworkenvironmentNotspeakingupKnowingDefinitionof DoneBusinessis opento ideasBusinessexpectationsare clear

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