ChallengingworkenvironmentTickets haveenoughdetail tocommitTicketsleft onboard toolongTalkingtoomuchPlanningeveryiterationNotspeakingupEffectiveestimationDifficulty incoordinationKnowingDefinitionof DoneNotpayingattentionForgettingTools/DocumentsTestingleft to theend of thesprintNeed torethinkfew waysof workingLearningculture isrespectedIgnoreproblemsBusinessexpectationsare clearSprintgoalshould bein placeFamiliarwith theroadmapBusinessis opento ideasOvercommittingorunderestimatingStretchinggoals tothe sprintClarity incommunicationin ADOCompromise ofquality due toimposeddeadlines,scope andresourcesProblemSolving inDailyScrumChallengingworkenvironmentTickets haveenoughdetail tocommitTicketsleft onboard toolongTalkingtoomuchPlanningeveryiterationNotspeakingupEffectiveestimationDifficulty incoordinationKnowingDefinitionof DoneNotpayingattentionForgettingTools/DocumentsTestingleft to theend of thesprintNeed torethinkfew waysof workingLearningculture isrespectedIgnoreproblemsBusinessexpectationsare clearSprintgoalshould bein placeFamiliarwith theroadmapBusinessis opento ideasOvercommittingorunderestimatingStretchinggoals tothe sprintClarity incommunicationin ADOCompromise ofquality due toimposeddeadlines,scope andresourcesProblemSolving inDailyScrum

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