KnowingDefinitionof DoneBusinessexpectationsare clearNotspeakingupCompromise ofquality due toimposeddeadlines,scope andresourcesIgnoreproblemsPlanningeveryiterationNotpayingattentionOvercommittingorunderestimatingDifficulty incoordinationFamiliarwith theroadmapForgettingTools/DocumentsTickets haveenoughdetail tocommitTalkingtoomuchTestingleft to theend of thesprintStretchinggoals tothe sprintClarity incommunicationin ADONeed torethinkfew waysof workingLearningculture isrespectedEffectiveestimationChallengingworkenvironmentProblemSolving inDailyScrumBusinessis opento ideasTicketsleft onboard toolongSprintgoalshould bein placeKnowingDefinitionof DoneBusinessexpectationsare clearNotspeakingupCompromise ofquality due toimposeddeadlines,scope andresourcesIgnoreproblemsPlanningeveryiterationNotpayingattentionOvercommittingorunderestimatingDifficulty incoordinationFamiliarwith theroadmapForgettingTools/DocumentsTickets haveenoughdetail tocommitTalkingtoomuchTestingleft to theend of thesprintStretchinggoals tothe sprintClarity incommunicationin ADONeed torethinkfew waysof workingLearningculture isrespectedEffectiveestimationChallengingworkenvironmentProblemSolving inDailyScrumBusinessis opento ideasTicketsleft onboard toolongSprintgoalshould bein place

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