OvercommittingorunderestimatingProblemSolving inDailyScrumcollaborationStretchinggoals to fitthe sprintUserstories notrefinedenoughEffectiveestimationClarity incommunicationin JIRAsprintflow isgoodIgnoreproblemsuntil lastminuteNotspeakingupexcitedaboutupcomingmilestonesscopecreepNeed torethinkfew waysof workingSprintgoal notclearNotenoughstructuretoomanymeetingsLearningculture isrespectedCompromise ofquality due toimposeddeadlines,scope andresourcesdeliverableexpectationsare clearnotanticipatingQA timeNotpayingattentionDefinition ofDone/Acceptancecriteria isclearno purposeto some ofthe meetingsChallengingworkenvironmentOvercommittingorunderestimatingProblemSolving inDailyScrumcollaborationStretchinggoals to fitthe sprintUserstories notrefinedenoughEffectiveestimationClarity incommunicationin JIRAsprintflow isgoodIgnoreproblemsuntil lastminuteNotspeakingupexcitedaboutupcomingmilestonesscopecreepNeed torethinkfew waysof workingSprintgoal notclearNotenoughstructuretoomanymeetingsLearningculture isrespectedCompromise ofquality due toimposeddeadlines,scope andresourcesdeliverableexpectationsare clearnotanticipatingQA timeNotpayingattentionDefinition ofDone/Acceptancecriteria isclearno purposeto some ofthe meetingsChallengingworkenvironment

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