ChallengingworkenvironmentDifficulty incoordinationTicketsleft onboard toolongProblemSolving inDailyScrumEffectiveestimationLearningculture isrespectedNeed torethinkfew waysof workingNotpayingattentionFamiliarwith theroadmapStretchinggoals tothe sprintPlanningeveryiterationClarity incommunicationin ADOKnowingDefinitionof DoneNotspeakingupBusinessis opento ideasTalkingtoomuchIgnoreproblemsBusinessexpectationsare clearCompromise ofquality due toimposeddeadlines,scope andresourcesTickets haveenoughdetail tocommitTestingleft to theend of thesprintSprintgoalshould bein placeForgettingTools/DocumentsOvercommittingorunderestimatingChallengingworkenvironmentDifficulty incoordinationTicketsleft onboard toolongProblemSolving inDailyScrumEffectiveestimationLearningculture isrespectedNeed torethinkfew waysof workingNotpayingattentionFamiliarwith theroadmapStretchinggoals tothe sprintPlanningeveryiterationClarity incommunicationin ADOKnowingDefinitionof DoneNotspeakingupBusinessis opento ideasTalkingtoomuchIgnoreproblemsBusinessexpectationsare clearCompromise ofquality due toimposeddeadlines,scope andresourcesTickets haveenoughdetail tocommitTestingleft to theend of thesprintSprintgoalshould bein placeForgettingTools/DocumentsOvercommittingorunderestimating

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