EffectiveestimationBacklogvisibility /nextsprintsCarryovereverysprintUnexpectedissuesAdd newtasks to thecurrent sprintafterplanningNeed torethinkfew waysof workingCompromise ofquality due tothe deadlines,scope andresourcesOvercommittingorunderestimatingClarity intickets inJIRATestingleft to theend of thesprintEffectivecommunicationPlanningeveryiterationAccess toenvironmentsGoogleerrorsDependenciesonstakeholdersor otherteamsA lot of/afewmeetingsEffectivenessin teamdeliverablesUse ofthe slackchannelSprintgoalsScrumsceremoniesDefinition ofDone/Acceptancecriteria is inplaceClear anddefinedarchitectureBusinessexpectationsare clear?CleardeadlinesEffectiveestimationBacklogvisibility /nextsprintsCarryovereverysprintUnexpectedissuesAdd newtasks to thecurrent sprintafterplanningNeed torethinkfew waysof workingCompromise ofquality due tothe deadlines,scope andresourcesOvercommittingorunderestimatingClarity intickets inJIRATestingleft to theend of thesprintEffectivecommunicationPlanningeveryiterationAccess toenvironmentsGoogleerrorsDependenciesonstakeholdersor otherteamsA lot of/afewmeetingsEffectivenessin teamdeliverablesUse ofthe slackchannelSprintgoalsScrumsceremoniesDefinition ofDone/Acceptancecriteria is inplaceClear anddefinedarchitectureBusinessexpectationsare clear?Cleardeadlines

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