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