CarryovereverysprintScrumsceremoniesPlanningeveryiterationSprintgoalsCompromise ofquality due tothe deadlines,scope andresourcesAccess toenvironmentsEffectivenessin teamdeliverablesCleardeadlinesNeed torethinkfew waysof workingBacklogvisibility /nextsprintsGoogleerrorsDependenciesonstakeholdersor otherteamsClarity intickets inJIRAEffectivecommunicationAdd newtasks to thecurrent sprintafterplanningA lot of/afewmeetingsOvercommittingorunderestimatingUnexpectedissuesEffectiveestimationTestingleft to theend of thesprintDefinition ofDone/Acceptancecriteria is inplaceUse ofthe slackchannelClear anddefinedarchitectureBusinessexpectationsare clear?CarryovereverysprintScrumsceremoniesPlanningeveryiterationSprintgoalsCompromise ofquality due tothe deadlines,scope andresourcesAccess toenvironmentsEffectivenessin teamdeliverablesCleardeadlinesNeed torethinkfew waysof workingBacklogvisibility /nextsprintsGoogleerrorsDependenciesonstakeholdersor otherteamsClarity intickets inJIRAEffectivecommunicationAdd newtasks to thecurrent sprintafterplanningA lot of/afewmeetingsOvercommittingorunderestimatingUnexpectedissuesEffectiveestimationTestingleft to theend of thesprintDefinition ofDone/Acceptancecriteria is inplaceUse ofthe slackchannelClear anddefinedarchitectureBusinessexpectationsare clear?

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