ProblemSolving inDailyScrumNotenoughstructureCompromise ofquality due toimposeddeadlines,scope andresourcesdeliverableexpectationsare clearLearningculture isrespectedStretchinggoals to fitthe sprinttoomanymeetingsIgnoreproblemsuntil lastminuteOvercommittingorunderestimatingscopecreepChallengingworkenvironmentNotpayingattentionnotanticipatingQA timeDefinition ofDone/Acceptancecriteria isclearsprintflow isgoodClarity incommunicationin JIRASprintgoal notclearUserstories notrefinedenoughcollaborationEffectiveestimationno purposeto some ofthe meetingsexcitedaboutupcomingmilestonesNeed torethinkfew waysof workingNotspeakingupProblemSolving inDailyScrumNotenoughstructureCompromise ofquality due toimposeddeadlines,scope andresourcesdeliverableexpectationsare clearLearningculture isrespectedStretchinggoals to fitthe sprinttoomanymeetingsIgnoreproblemsuntil lastminuteOvercommittingorunderestimatingscopecreepChallengingworkenvironmentNotpayingattentionnotanticipatingQA timeDefinition ofDone/Acceptancecriteria isclearsprintflow isgoodClarity incommunicationin JIRASprintgoal notclearUserstories notrefinedenoughcollaborationEffectiveestimationno purposeto some ofthe meetingsexcitedaboutupcomingmilestonesNeed torethinkfew waysof workingNotspeakingup

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