CarryovereverysprintAdd newtasks to thecurrent sprintafterplanningClarity intickets inJIRASprintgoalsCleardeadlinesUnexpectedissuesA lot of/afewmeetingsTestingleft to theend of thesprintCompromise ofquality due tothe deadlines,scope andresourcesDependenciesonstakeholdersor otherteamsUse ofthe slackchannelScrumsceremoniesAccess toenvironmentsEffectivenessin teamdeliverablesClear anddefinedarchitectureNeed torethinkfew waysof workingEffectiveestimationGoogleerrorsBusinessexpectationsare clear?PlanningeveryiterationBacklogvisibility /nextsprintsOvercommittingorunderestimatingDefinition ofDone/Acceptancecriteria is inplaceEffectivecommunicationCarryovereverysprintAdd newtasks to thecurrent sprintafterplanningClarity intickets inJIRASprintgoalsCleardeadlinesUnexpectedissuesA lot of/afewmeetingsTestingleft to theend of thesprintCompromise ofquality due tothe deadlines,scope andresourcesDependenciesonstakeholdersor otherteamsUse ofthe slackchannelScrumsceremoniesAccess toenvironmentsEffectivenessin teamdeliverablesClear anddefinedarchitectureNeed torethinkfew waysof workingEffectiveestimationGoogleerrorsBusinessexpectationsare clear?PlanningeveryiterationBacklogvisibility /nextsprintsOvercommittingorunderestimatingDefinition ofDone/Acceptancecriteria is inplaceEffectivecommunication

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