TOMISClarity incommunicationin JIRASEACATSTalkingtoomuchDefinitionof DoneAutomationofmonitoringRetrospectiveImpedimentsIgnoreproblemsClearlyWrittenSubtasks3 WeekSprintFACTSCompromise ofquality due toimposeddeadlines,scope andresourcesFACTSCoordinationEffectiveestimationPostScrumForgettingArtefacts/Tools/DocumentsProof ofConceptPlanningeveryiterationClearDescriptionNotspeakingupTestingleft to theend of thesprintProblemSolving inDailyScrumSprintgoalshould bein placeBDWLogWorkDailyEffectiveEstimationBO/POspecifyingsolutionsAreas forImprovementNotpayingattentionDifficulty incoordinationDailyScrumBusinessis opento ideasASFLearningculture isrespectedOpenissuestriageprocessDefinition ofDone/Acceptancecriteria is inplaceRegressionTestAd-hocWorkStretchinggoals tothe sprintJICMSBusinessexpectationsare clearChallengingworkenvironmentOvercommittingorunderestimatingNeed torethinkfew waysof workingAgileTeamClearBusinessDescriptionIterationTOMISClarity incommunicationin JIRASEACATSTalkingtoomuchDefinitionof DoneAutomationofmonitoringRetrospectiveImpedimentsIgnoreproblemsClearlyWrittenSubtasks3 WeekSprintFACTSCompromise ofquality due toimposeddeadlines,scope andresourcesFACTSCoordinationEffectiveestimationPostScrumForgettingArtefacts/Tools/DocumentsProof ofConceptPlanningeveryiterationClearDescriptionNotspeakingupTestingleft to theend of thesprintProblemSolving inDailyScrumSprintgoalshould bein placeBDWLogWorkDailyEffectiveEstimationBO/POspecifyingsolutionsAreas forImprovementNotpayingattentionDifficulty incoordinationDailyScrumBusinessis opento ideasASFLearningculture isrespectedOpenissuestriageprocessDefinition ofDone/Acceptancecriteria is inplaceRegressionTestAd-hocWorkStretchinggoals tothe sprintJICMSBusinessexpectationsare clearChallengingworkenvironmentOvercommittingorunderestimatingNeed torethinkfew waysof workingAgileTeamClearBusinessDescriptionIteration

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