Testingleft to theend of thesprintSprintgoalsDefinition ofDone/Acceptancecriteria is inplaceAccess toenvironmentsOvercommittingorunderestimatingNeed torethinkfew waysof workingClear anddefinedarchitectureCompromise ofquality due tothe deadlines,scope andresourcesEffectiveestimationEffectivenessin teamdeliverablesScrumsceremoniesPlanningeveryiterationClarity intickets inJIRACarryovereverysprintA lot of/afewmeetingsEffectivecommunicationAdd newtasks to thecurrent sprintafterplanningGoogleerrorsBusinessexpectationsare clear?Backlogvisibility /nextsprintsDependenciesonstakeholdersor otherteamsUnexpectedissuesUse ofthe slackchannelCleardeadlinesTestingleft to theend of thesprintSprintgoalsDefinition ofDone/Acceptancecriteria is inplaceAccess toenvironmentsOvercommittingorunderestimatingNeed torethinkfew waysof workingClear anddefinedarchitectureCompromise ofquality due tothe deadlines,scope andresourcesEffectiveestimationEffectivenessin teamdeliverablesScrumsceremoniesPlanningeveryiterationClarity intickets inJIRACarryovereverysprintA lot of/afewmeetingsEffectivecommunicationAdd newtasks to thecurrent sprintafterplanningGoogleerrorsBusinessexpectationsare clear?Backlogvisibility /nextsprintsDependenciesonstakeholdersor otherteamsUnexpectedissuesUse ofthe slackchannelCleardeadlines

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