BO/POspecifyingsolutionsLearningculture isrespectedEffectiveestimationDifficulty incoordinationProblemSolving inDailyScrumSprintgoalshould bein placeDefinition ofDone/Acceptancecriteria is inplaceCompromise ofquality due toimposeddeadlines,scope andresourcesNotspeakingupTestingleft to theend of thesprintIgnoreproblemsTalkingtoomuchBusinessis opento ideasNotpayingattentionStretchinggoals tothe sprintChallengingworkenvironmentForgettingArtefacts/Tools/DocumentsNeed torethinkfew waysof workingOvercommittingorunderestimatingClarity incommunicationin TFSOpenissuestriageprocessPlanningeveryiterationBusinessexpectationsare clearAutomationofmonitoringBO/POspecifyingsolutionsLearningculture isrespectedEffectiveestimationDifficulty incoordinationProblemSolving inDailyScrumSprintgoalshould bein placeDefinition ofDone/Acceptancecriteria is inplaceCompromise ofquality due toimposeddeadlines,scope andresourcesNotspeakingupTestingleft to theend of thesprintIgnoreproblemsTalkingtoomuchBusinessis opento ideasNotpayingattentionStretchinggoals tothe sprintChallengingworkenvironmentForgettingArtefacts/Tools/DocumentsNeed torethinkfew waysof workingOvercommittingorunderestimatingClarity incommunicationin TFSOpenissuestriageprocessPlanningeveryiterationBusinessexpectationsare clearAutomationofmonitoring

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