Clear anddefinedarchitectureSprintgoalsEffectivenessin teamdeliverablesOvercommittingorunderestimatingAccess toenvironmentsBacklogvisibility /nextsprintsUse ofthe slackchannelScrumsceremoniesAdd newtasks to thecurrent sprintafterplanningDefinition ofDone/Acceptancecriteria is inplaceGoogleerrorsCompromise ofquality due tothe deadlines,scope andresourcesA lot of/afewmeetingsUnexpectedissuesCarryovereverysprintNeed torethinkfew waysof workingPlanningeveryiterationEffectivecommunicationClarity intickets inJIRACleardeadlinesBusinessexpectationsare clear?EffectiveestimationTestingleft to theend of thesprintDependenciesonstakeholdersor otherteamsClear anddefinedarchitectureSprintgoalsEffectivenessin teamdeliverablesOvercommittingorunderestimatingAccess toenvironmentsBacklogvisibility /nextsprintsUse ofthe slackchannelScrumsceremoniesAdd newtasks to thecurrent sprintafterplanningDefinition ofDone/Acceptancecriteria is inplaceGoogleerrorsCompromise ofquality due tothe deadlines,scope andresourcesA lot of/afewmeetingsUnexpectedissuesCarryovereverysprintNeed torethinkfew waysof workingPlanningeveryiterationEffectivecommunicationClarity intickets inJIRACleardeadlinesBusinessexpectationsare clear?EffectiveestimationTestingleft to theend of thesprintDependenciesonstakeholdersor otherteams

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