ChallengingworkenvironmentBusinessis opento ideasBusinessexpectationsare clearTalkingtoomuchTicketsleft onboard toolongEffectiveestimationFamiliarwith theroadmapLearningculture isrespectedSprintgoalshould bein placeProblemSolving inDailyScrumNeed torethinkfew waysof workingOvercommittingorunderestimatingNotspeakingupClarity incommunicationin ADODifficulty incoordinationTickets haveenoughdetail tocommitNotpayingattentionIgnoreproblemsStretchinggoals tothe sprintForgettingTools/DocumentsPlanningeveryiterationTestingleft to theend of thesprintKnowingDefinitionof DoneCompromise ofquality due toimposeddeadlines,scope andresourcesChallengingworkenvironmentBusinessis opento ideasBusinessexpectationsare clearTalkingtoomuchTicketsleft onboard toolongEffectiveestimationFamiliarwith theroadmapLearningculture isrespectedSprintgoalshould bein placeProblemSolving inDailyScrumNeed torethinkfew waysof workingOvercommittingorunderestimatingNotspeakingupClarity incommunicationin ADODifficulty incoordinationTickets haveenoughdetail tocommitNotpayingattentionIgnoreproblemsStretchinggoals tothe sprintForgettingTools/DocumentsPlanningeveryiterationTestingleft to theend of thesprintKnowingDefinitionof DoneCompromise ofquality due toimposeddeadlines,scope andresources

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