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