EffectiveestimationBusinessexpectationsare clearNotspeakingupOpenissuestriageprocessSprintgoalshould bein placeDifficulty incoordinationForgettingArtefacts/Tools/DocumentsChallengingworkenvironmentTestingleft to theend of thesprintProblemSolving inDailyScrumCompromise ofquality due toimposeddeadlines,scope andresourcesIgnoreproblemsTalkingtoomuchAutomationofmonitoringOvercommittingorunderestimatingBusinessis opento ideasNeed torethinkfew waysof workingStretchinggoals tothe sprintLearningculture isrespectedBO/POspecifyingsolutionsNotpayingattentionClarity incommunicationin JIRADefinition ofDone/Acceptancecriteria is inplacePlanningeveryiterationEffectiveestimationBusinessexpectationsare clearNotspeakingupOpenissuestriageprocessSprintgoalshould bein placeDifficulty incoordinationForgettingArtefacts/Tools/DocumentsChallengingworkenvironmentTestingleft to theend of thesprintProblemSolving inDailyScrumCompromise ofquality due toimposeddeadlines,scope andresourcesIgnoreproblemsTalkingtoomuchAutomationofmonitoringOvercommittingorunderestimatingBusinessis opento ideasNeed torethinkfew waysof workingStretchinggoals tothe sprintLearningculture isrespectedBO/POspecifyingsolutionsNotpayingattentionClarity incommunicationin JIRADefinition ofDone/Acceptancecriteria is inplacePlanningeveryiteration

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