Clarity incommunicationin JIRAno purposeto some ofthe meetingsNeed torethinkfew waysof workingnotanticipatingQA timeChallengingworkenvironmentUserstories notrefinedenoughexcitedaboutupcomingmilestonesOvercommittingorunderestimatingNotspeakingupcollaborationIgnoreproblemsuntil lastminuteNotenoughstructureStretchinggoals to fitthe sprintdeliverableexpectationsare clearsprintflow isgoodCompromise ofquality due toimposeddeadlines,scope andresourcesDefinition ofDone/Acceptancecriteria isclearEffectiveestimationtoomanymeetingsSprintgoal notclearProblemSolving inDailyScrumLearningculture isrespectedNotpayingattentionscopecreepClarity incommunicationin JIRAno purposeto some ofthe meetingsNeed torethinkfew waysof workingnotanticipatingQA timeChallengingworkenvironmentUserstories notrefinedenoughexcitedaboutupcomingmilestonesOvercommittingorunderestimatingNotspeakingupcollaborationIgnoreproblemsuntil lastminuteNotenoughstructureStretchinggoals to fitthe sprintdeliverableexpectationsare clearsprintflow isgoodCompromise ofquality due toimposeddeadlines,scope andresourcesDefinition ofDone/Acceptancecriteria isclearEffectiveestimationtoomanymeetingsSprintgoal notclearProblemSolving inDailyScrumLearningculture isrespectedNotpayingattentionscopecreep

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