RegressionTestProblemSolving inDailyScrumAgileTeamDefinitionof DoneAutomationofmonitoringCoordinationJICMSClearlyWrittenSubtasksAreas forImprovementClearBusinessDescriptionNeed torethinkfew waysof workingIgnoreproblemsLearningculture isrespectedIterationFACTSPlanningeveryiterationBO/POspecifyingsolutionsImpedimentsChallengingworkenvironmentDailyScrumOpenissuestriageprocessStretchinggoals tothe sprint3 WeekSprintEffectiveestimationClearDescriptionSEACATSLogWorkDailyTalkingtoomuchDefinition ofDone/Acceptancecriteria is inplacePostScrumNotspeakingupASFProof ofConceptClarity incommunicationin JIRASprintgoalshould bein placeFACTSRetrospectiveBusinessexpectationsare clearCompromise ofquality due toimposeddeadlines,scope andresourcesTOMISNotpayingattentionAd-hocWorkEffectiveEstimationBDWTestingleft to theend of thesprintForgettingArtefacts/Tools/DocumentsDifficulty incoordinationBusinessis opento ideasOvercommittingorunderestimatingRegressionTestProblemSolving inDailyScrumAgileTeamDefinitionof DoneAutomationofmonitoringCoordinationJICMSClearlyWrittenSubtasksAreas forImprovementClearBusinessDescriptionNeed torethinkfew waysof workingIgnoreproblemsLearningculture isrespectedIterationFACTSPlanningeveryiterationBO/POspecifyingsolutionsImpedimentsChallengingworkenvironmentDailyScrumOpenissuestriageprocessStretchinggoals tothe sprint3 WeekSprintEffectiveestimationClearDescriptionSEACATSLogWorkDailyTalkingtoomuchDefinition ofDone/Acceptancecriteria is inplacePostScrumNotspeakingupASFProof ofConceptClarity incommunicationin JIRASprintgoalshould bein placeFACTSRetrospectiveBusinessexpectationsare clearCompromise ofquality due toimposeddeadlines,scope andresourcesTOMISNotpayingattentionAd-hocWorkEffectiveEstimationBDWTestingleft to theend of thesprintForgettingArtefacts/Tools/DocumentsDifficulty incoordinationBusinessis opento ideasOvercommittingorunderestimating

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
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
  1. Regression Test
  2. Problem Solving in Daily Scrum
  3. Agile Team
  4. Definition of Done
  5. Automation of monitoring
  6. Coordination
  7. JICMS
  8. Clearly Written Subtasks
  9. Areas for Improvement
  10. Clear Business Description
  11. Need to rethink few ways of working
  12. Ignore problems
  13. Learning culture is respected
  14. Iteration
  15. FACTS
  16. Planning every iteration
  17. BO/PO specifying solutions
  18. Impediments
  19. Challenging work environment
  20. Daily Scrum
  21. Open issues triage process
  22. Stretching goals to the sprint
  23. 3 Week Sprint
  24. Effective estimation
  25. Clear Description
  26. SEACATS
  27. Log Work Daily
  28. Talking too much
  29. Definition of Done/ Acceptance criteria is in place
  30. Post Scrum
  31. Not speaking up
  32. ASF
  33. Proof of Concept
  34. Clarity in communication in JIRA
  35. Sprint goal should be in place
  36. FACTS
  37. Retrospective
  38. Business expectations are clear
  39. Compromise of quality due to imposed deadlines, scope and resources
  40. TOMIS
  41. Not paying attention
  42. Ad-hoc Work
  43. Effective Estimation
  44. BDW
  45. Testing left to the end of the sprint
  46. Forgetting Artefacts/Tools/Documents
  47. Difficulty in coordination
  48. Business is open to ideas
  49. Overcommitting or underestimating