Need torethinkfew waysof workingNotspeakingupFamiliarwith theroadmapClarity incommunicationin ADOTickets haveenoughdetail tocommitEffectiveestimationOvercommittingorunderestimatingTalkingtoomuchCompromise ofquality due toimposeddeadlines,scope andresourcesPlanningeveryiterationTestingleft to theend of thesprintStretchinggoals tothe sprintProblemSolving inDailyScrumBusinessis opento ideasDifficulty incoordinationKnowingDefinitionof DoneNotpayingattentionChallengingworkenvironmentTicketsleft onboard toolongSprintgoalshould bein placeForgettingTools/DocumentsBusinessexpectationsare clearLearningculture isrespectedIgnoreproblemsNeed torethinkfew waysof workingNotspeakingupFamiliarwith theroadmapClarity incommunicationin ADOTickets haveenoughdetail tocommitEffectiveestimationOvercommittingorunderestimatingTalkingtoomuchCompromise ofquality due toimposeddeadlines,scope andresourcesPlanningeveryiterationTestingleft to theend of thesprintStretchinggoals tothe sprintProblemSolving inDailyScrumBusinessis opento ideasDifficulty incoordinationKnowingDefinitionof DoneNotpayingattentionChallengingworkenvironmentTicketsleft onboard toolongSprintgoalshould bein placeForgettingTools/DocumentsBusinessexpectationsare clearLearningculture isrespectedIgnoreproblems

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