NotenoughstructureNotpayingattentionUserstories notrefinedenoughNeed torethinkfew waysof workingClarity incommunicationin JIRACompromise ofquality due toimposeddeadlines,scope andresourcesChallengingworkenvironmentNotspeakingupno purposeto some ofthe meetingsOvercommittingorunderestimatingnotanticipatingQA timeexcitedaboutupcomingmilestonesscopecreeptoomanymeetingsIgnoreproblemsuntil lastminutecollaborationProblemSolving inDailyScrumEffectiveestimationLearningculture isrespecteddeliverableexpectationsare clearStretchinggoals to fitthe sprintSprintgoal notclearsprintflow isgoodDefinition ofDone/Acceptancecriteria isclearNotenoughstructureNotpayingattentionUserstories notrefinedenoughNeed torethinkfew waysof workingClarity incommunicationin JIRACompromise ofquality due toimposeddeadlines,scope andresourcesChallengingworkenvironmentNotspeakingupno purposeto some ofthe meetingsOvercommittingorunderestimatingnotanticipatingQA timeexcitedaboutupcomingmilestonesscopecreeptoomanymeetingsIgnoreproblemsuntil lastminutecollaborationProblemSolving inDailyScrumEffectiveestimationLearningculture isrespecteddeliverableexpectationsare clearStretchinggoals to fitthe sprintSprintgoal notclearsprintflow isgoodDefinition ofDone/Acceptancecriteria isclear

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