Need torethinkfew waysof workingStretchinggoals to fitthe sprintexcitedaboutupcomingmilestonesChallengingworkenvironmentDefinition ofDone/Acceptancecriteria isclearNotpayingattentiondeliverableexpectationsare clearProblemSolving inDailyScrumIgnoreproblemsuntil lastminutescopecreepsprintflow isgoodtoomanymeetingsClarity incommunicationin JIRAOvercommittingorunderestimatingCompromise ofquality due toimposeddeadlines,scope andresourcesEffectiveestimationNotenoughstructureUserstories notrefinedenoughcollaborationnotanticipatingQA timeNotspeakingupno purposeto some ofthe meetingsLearningculture isrespectedSprintgoal notclearNeed torethinkfew waysof workingStretchinggoals to fitthe sprintexcitedaboutupcomingmilestonesChallengingworkenvironmentDefinition ofDone/Acceptancecriteria isclearNotpayingattentiondeliverableexpectationsare clearProblemSolving inDailyScrumIgnoreproblemsuntil lastminutescopecreepsprintflow isgoodtoomanymeetingsClarity incommunicationin JIRAOvercommittingorunderestimatingCompromise ofquality due toimposeddeadlines,scope andresourcesEffectiveestimationNotenoughstructureUserstories notrefinedenoughcollaborationnotanticipatingQA timeNotspeakingupno purposeto some ofthe meetingsLearningculture isrespectedSprintgoal notclear

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