Ignoreproblemsuntil lastminuteSprintgoal notclearCompromise ofquality due toimposeddeadlines,scope andresourcesNotpayingattentionNeed torethinkfew waysof workingProblemSolving inDailyScrumNotenoughstructureStretchinggoals to fitthe sprintOvercommittingorunderestimatingno purposeto some ofthe meetingstoomanymeetingsUserstories notrefinedenoughnotanticipatingQA timeexcitedaboutupcomingmilestonesscopecreepChallengingworkenvironmentDefinition ofDone/Acceptancecriteria isclearNotspeakingupcollaborationLearningculture isrespectedClarity incommunicationin JIRAdeliverableexpectationsare clearEffectiveestimationsprintflow isgoodIgnoreproblemsuntil lastminuteSprintgoal notclearCompromise ofquality due toimposeddeadlines,scope andresourcesNotpayingattentionNeed torethinkfew waysof workingProblemSolving inDailyScrumNotenoughstructureStretchinggoals to fitthe sprintOvercommittingorunderestimatingno purposeto some ofthe meetingstoomanymeetingsUserstories notrefinedenoughnotanticipatingQA timeexcitedaboutupcomingmilestonesscopecreepChallengingworkenvironmentDefinition ofDone/Acceptancecriteria isclearNotspeakingupcollaborationLearningculture isrespectedClarity incommunicationin JIRAdeliverableexpectationsare clearEffectiveestimationsprintflow isgood

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