EffectivecommunicationSprintgoalsClear anddefinedarchitecturePlanningeveryiterationEffectivenessin teamdeliverablesDefinition ofDone/Acceptancecriteria is inplaceNeed torethinkfew waysof workingEffectiveestimationCompromise ofquality due tothe deadlines,scope andresourcesClarity intickets inJIRATestingleft to theend of thesprintUse ofthe slackchannelBusinessexpectationsare clear?GoogleerrorsA lot of/afewmeetingsOvercommittingorunderestimatingDependenciesonstakeholdersor otherteamsCarryovereverysprintAdd newtasks to thecurrent sprintafterplanningCleardeadlinesAccess toenvironmentsUnexpectedissuesBacklogvisibility /nextsprintsScrumsceremoniesEffectivecommunicationSprintgoalsClear anddefinedarchitecturePlanningeveryiterationEffectivenessin teamdeliverablesDefinition ofDone/Acceptancecriteria is inplaceNeed torethinkfew waysof workingEffectiveestimationCompromise ofquality due tothe deadlines,scope andresourcesClarity intickets inJIRATestingleft to theend of thesprintUse ofthe slackchannelBusinessexpectationsare clear?GoogleerrorsA lot of/afewmeetingsOvercommittingorunderestimatingDependenciesonstakeholdersor otherteamsCarryovereverysprintAdd newtasks to thecurrent sprintafterplanningCleardeadlinesAccess toenvironmentsUnexpectedissuesBacklogvisibility /nextsprintsScrumsceremonies

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