ProblemSolving inDailyScrumOvercommittingorunderestimatingCompromise ofquality due toimposeddeadlines,scope andresourcesBusinessexpectationsare clearIgnoreproblemsBusinessis opento ideasChallengingworkenvironmentAutomationofmonitoringForgettingArtefacts/Tools/DocumentsSprintgoalshould bein placeNotpayingattentionLearningculture isrespectedPlanningeveryiterationDifficulty incoordinationOpenissuestriageprocessNotspeakingupEffectiveestimationBO/POspecifyingsolutionsNeed torethinkfew waysof workingTalkingtoomuchDefinition ofDone/Acceptancecriteria is inplaceClarity incommunicationin JIRATestingleft to theend of thesprintStretchinggoals tothe sprintProblemSolving inDailyScrumOvercommittingorunderestimatingCompromise ofquality due toimposeddeadlines,scope andresourcesBusinessexpectationsare clearIgnoreproblemsBusinessis opento ideasChallengingworkenvironmentAutomationofmonitoringForgettingArtefacts/Tools/DocumentsSprintgoalshould bein placeNotpayingattentionLearningculture isrespectedPlanningeveryiterationDifficulty incoordinationOpenissuestriageprocessNotspeakingupEffectiveestimationBO/POspecifyingsolutionsNeed torethinkfew waysof workingTalkingtoomuchDefinition ofDone/Acceptancecriteria is inplaceClarity incommunicationin JIRATestingleft to theend of thesprintStretchinggoals tothe sprint

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. Problem Solving in Daily Scrum
  2. Overcommitting or underestimating
  3. Compromise of quality due to imposed deadlines, scope and resources
  4. Business expectations are clear
  5. Ignore problems
  6. Business is open to ideas
  7. Challenging work environment
  8. Automation of monitoring
  9. Forgetting Artefacts/Tools/Documents
  10. Sprint goal should be in place
  11. Not paying attention
  12. Learning culture is respected
  13. Planning every iteration
  14. Difficulty in coordination
  15. Open issues triage process
  16. Not speaking up
  17. Effective estimation
  18. BO/PO specifying solutions
  19. Need to rethink few ways of working
  20. Talking too much
  21. Definition of Done/ Acceptance criteria is in place
  22. Clarity in communication in JIRA
  23. Testing left to the end of the sprint
  24. Stretching goals to the sprint