Overcommittingorunderestimatingno purposeto some ofthe meetingsDefinition ofDone/Acceptancecriteria isclearLearningculture isrespectedClarity incommunicationin JIRAcollaborationProblemSolving inDailyScrumCompromise ofquality due toimposeddeadlines,scope andresourcesexcitedaboutupcomingmilestonesdeliverableexpectationsare clearNotspeakingupUserstories notrefinedenoughsprintflow isgoodNotpayingattentionEffectiveestimationIgnoreproblemsuntil lastminuteChallengingworkenvironmentStretchinggoals to fitthe sprintNeed torethinkfew waysof workingtoomanymeetingsSprintgoal notclearscopecreepNotenoughstructurenotanticipatingQA timeOvercommittingorunderestimatingno purposeto some ofthe meetingsDefinition ofDone/Acceptancecriteria isclearLearningculture isrespectedClarity incommunicationin JIRAcollaborationProblemSolving inDailyScrumCompromise ofquality due toimposeddeadlines,scope andresourcesexcitedaboutupcomingmilestonesdeliverableexpectationsare clearNotspeakingupUserstories notrefinedenoughsprintflow isgoodNotpayingattentionEffectiveestimationIgnoreproblemsuntil lastminuteChallengingworkenvironmentStretchinggoals to fitthe sprintNeed torethinkfew waysof workingtoomanymeetingsSprintgoal notclearscopecreepNotenoughstructurenotanticipatingQA time

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