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