Clarity incommunicationin ADOChallengingworkenvironmentProblemSolving inDailyScrumBusinessexpectationsare clearDifficulty incoordinationCompromise ofquality due toimposeddeadlines,scope andresourcesStretchinggoals tothe sprintLearningculture isrespectedNeed torethinkfew waysof workingPlanningeveryiterationTalkingtoomuchNotspeakingupBusinessis opento ideasNotpayingattentionIgnoreproblemsTickets haveenoughdetail tocommitKnowingDefinitionof DoneEffectiveestimationFamiliarwith theroadmapTestingleft to theend of thesprintForgettingTools/DocumentsOvercommittingorunderestimatingTicketsleft onboard toolongSprintgoalshould bein placeClarity incommunicationin ADOChallengingworkenvironmentProblemSolving inDailyScrumBusinessexpectationsare clearDifficulty incoordinationCompromise ofquality due toimposeddeadlines,scope andresourcesStretchinggoals tothe sprintLearningculture isrespectedNeed torethinkfew waysof workingPlanningeveryiterationTalkingtoomuchNotspeakingupBusinessis opento ideasNotpayingattentionIgnoreproblemsTickets haveenoughdetail tocommitKnowingDefinitionof DoneEffectiveestimationFamiliarwith theroadmapTestingleft to theend of thesprintForgettingTools/DocumentsOvercommittingorunderestimatingTicketsleft onboard toolongSprintgoalshould bein place

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