no purposeto some ofthe meetingsStretchinggoals to fitthe sprintSprintgoal notclearProblemSolving inDailyScrumCompromise ofquality due toimposeddeadlines,scope andresourcesNotpayingattentionNotenoughstructureLearningculture isrespectedIgnoreproblemsuntil lastminuteexcitedaboutupcomingmilestonesOvercommittingorunderestimatingNeed torethinkfew waysof workingsprintflow isgoodEffectiveestimationdeliverableexpectationsare clearcollaborationUserstories notrefinedenoughnotanticipatingQA timeNotspeakingupClarity incommunicationin JIRAscopecreepChallengingworkenvironmentDefinition ofDone/Acceptancecriteria iscleartoomanymeetingsno purposeto some ofthe meetingsStretchinggoals to fitthe sprintSprintgoal notclearProblemSolving inDailyScrumCompromise ofquality due toimposeddeadlines,scope andresourcesNotpayingattentionNotenoughstructureLearningculture isrespectedIgnoreproblemsuntil lastminuteexcitedaboutupcomingmilestonesOvercommittingorunderestimatingNeed torethinkfew waysof workingsprintflow isgoodEffectiveestimationdeliverableexpectationsare clearcollaborationUserstories notrefinedenoughnotanticipatingQA timeNotspeakingupClarity incommunicationin JIRAscopecreepChallengingworkenvironmentDefinition ofDone/Acceptancecriteria iscleartoomanymeetings

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