Testingleft to theend of thesprintCarryovereverysprintUnexpectedissuesEffectivecommunicationAccess toenvironmentsGoogleerrorsAdd newtasks to thecurrent sprintafterplanningEffectivenessin teamdeliverablesEffectiveestimationCleardeadlinesScrumsceremoniesPlanningeveryiterationUse ofthe slackchannelNeed torethinkfew waysof workingClarity intickets inJIRADefinition ofDone/Acceptancecriteria is inplaceSprintgoalsBusinessexpectationsare clear?Clear anddefinedarchitectureDependenciesonstakeholdersor otherteamsOvercommittingorunderestimatingBacklogvisibility /nextsprintsA lot of/afewmeetingsCompromise ofquality due tothe deadlines,scope andresourcesTestingleft to theend of thesprintCarryovereverysprintUnexpectedissuesEffectivecommunicationAccess toenvironmentsGoogleerrorsAdd newtasks to thecurrent sprintafterplanningEffectivenessin teamdeliverablesEffectiveestimationCleardeadlinesScrumsceremoniesPlanningeveryiterationUse ofthe slackchannelNeed torethinkfew waysof workingClarity intickets inJIRADefinition ofDone/Acceptancecriteria is inplaceSprintgoalsBusinessexpectationsare clear?Clear anddefinedarchitectureDependenciesonstakeholdersor otherteamsOvercommittingorunderestimatingBacklogvisibility /nextsprintsA lot of/afewmeetingsCompromise ofquality due tothe deadlines,scope andresources

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. Testing left to the end of the sprint
  2. Carry over every sprint
  3. Unexpected issues
  4. Effective communication
  5. Access to environments
  6. Google errors
  7. Add new tasks to the current sprint after planning
  8. Effectiveness in team deliverables
  9. Effective estimation
  10. Clear deadlines
  11. Scrums ceremonies
  12. Planning every iteration
  13. Use of the slack channel
  14. Need to rethink few ways of working
  15. Clarity in tickets in JIRA
  16. Definition of Done/ Acceptance criteria is in place
  17. Sprint goals
  18. Business expectations are clear?
  19. Clear and defined architecture
  20. Dependencies on stakeholders or other teams
  21. Overcommitting or underestimating
  22. Backlog visibility / next sprints
  23. A lot of/a few meetings
  24. Compromise of quality due to the deadlines, scope and resources