Clarity incommunicationin JIRALearningculture isrespectedscopecreepNotspeakingupIgnoreproblemsuntil lastminuteStretchinggoals to fitthe sprintDefinition ofDone/Acceptancecriteria isclearNotpayingattentiondeliverableexpectationsare cleartoomanymeetingsChallengingworkenvironmentCompromise ofquality due toimposeddeadlines,scope andresourcesNotenoughstructureProblemSolving inDailyScrumcollaborationOvercommittingorunderestimatingNeed torethinkfew waysof workingEffectiveestimationsprintflow isgoodexcitedaboutupcomingmilestonesSprintgoal notclearUserstories notrefinedenoughno purposeto some ofthe meetingsnotanticipatingQA timeClarity incommunicationin JIRALearningculture isrespectedscopecreepNotspeakingupIgnoreproblemsuntil lastminuteStretchinggoals to fitthe sprintDefinition ofDone/Acceptancecriteria isclearNotpayingattentiondeliverableexpectationsare cleartoomanymeetingsChallengingworkenvironmentCompromise ofquality due toimposeddeadlines,scope andresourcesNotenoughstructureProblemSolving inDailyScrumcollaborationOvercommittingorunderestimatingNeed torethinkfew waysof workingEffectiveestimationsprintflow isgoodexcitedaboutupcomingmilestonesSprintgoal notclearUserstories notrefinedenoughno purposeto some ofthe meetingsnotanticipatingQA time

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