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