Businessexpectationsare clearForgettingTools/DocumentsCompromise ofquality due toimposeddeadlines,scope andresourcesNotpayingattentionLearningculture isrespectedBusinessis opento ideasOvercommittingorunderestimatingProblemSolving inDailyScrumChallengingworkenvironmentSprintgoalshould bein placeEffectiveestimationPlanningeveryiterationStretchinggoals tothe sprintDifficulty incoordinationTickets haveenoughdetail tocommitTalkingtoomuchNeed torethinkfew waysof workingTicketsleft onboard toolongKnowingDefinitionof DoneTestingleft to theend of thesprintNotspeakingupFamiliarwith theroadmapIgnoreproblemsClarity incommunicationin ADOBusinessexpectationsare clearForgettingTools/DocumentsCompromise ofquality due toimposeddeadlines,scope andresourcesNotpayingattentionLearningculture isrespectedBusinessis opento ideasOvercommittingorunderestimatingProblemSolving inDailyScrumChallengingworkenvironmentSprintgoalshould bein placeEffectiveestimationPlanningeveryiterationStretchinggoals tothe sprintDifficulty incoordinationTickets haveenoughdetail tocommitTalkingtoomuchNeed torethinkfew waysof workingTicketsleft onboard toolongKnowingDefinitionof DoneTestingleft to theend of thesprintNotspeakingupFamiliarwith theroadmapIgnoreproblemsClarity incommunicationin ADO

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