Sprintgoal notclearChallengingworkenvironmentDefinition ofDone/Acceptancecriteria isclearOvercommittingorunderestimatingLearningculture isrespectedClarity incommunicationin JIRAscopecreepcollaborationno purposeto some ofthe meetingsNotpayingattentiondeliverableexpectationsare clearsprintflow isgoodStretchinggoals to fitthe sprintNeed torethinkfew waysof workingexcitedaboutupcomingmilestonesUserstories notrefinedenoughnotanticipatingQA timeCompromise ofquality due toimposeddeadlines,scope andresourcesIgnoreproblemsuntil lastminuteNotspeakingupNotenoughstructuretoomanymeetingsEffectiveestimationProblemSolving inDailyScrumSprintgoal notclearChallengingworkenvironmentDefinition ofDone/Acceptancecriteria isclearOvercommittingorunderestimatingLearningculture isrespectedClarity incommunicationin JIRAscopecreepcollaborationno purposeto some ofthe meetingsNotpayingattentiondeliverableexpectationsare clearsprintflow isgoodStretchinggoals to fitthe sprintNeed torethinkfew waysof workingexcitedaboutupcomingmilestonesUserstories notrefinedenoughnotanticipatingQA timeCompromise ofquality due toimposeddeadlines,scope andresourcesIgnoreproblemsuntil lastminuteNotspeakingupNotenoughstructuretoomanymeetingsEffectiveestimationProblemSolving inDailyScrum

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. Sprint goal not clear
  2. Challenging work environment
  3. Definition of Done/ Acceptance criteria is clear
  4. Overcommitting or underestimating
  5. Learning culture is respected
  6. Clarity in communication in JIRA
  7. scope creep
  8. collaboration
  9. no purpose to some of the meetings
  10. Not paying attention
  11. deliverable expectations are clear
  12. sprint flow is good
  13. Stretching goals to fit the sprint
  14. Need to rethink few ways of working
  15. excited about upcoming milestones
  16. User stories not refined enough
  17. not anticipating QA time
  18. Compromise of quality due to imposed deadlines, scope and resources
  19. Ignore problems until last minute
  20. Not speaking up
  21. Not enough structure
  22. too many meetings
  23. Effective estimation
  24. Problem Solving in Daily Scrum