Backlogvisibility /nextsprintsUse ofthe slackchannelEffectivecommunicationCompromise ofquality due tothe deadlines,scope andresourcesBusinessexpectationsare clear?Effectivenessin teamdeliverablesEffectiveestimationNeed torethinkfew waysof workingAccess toenvironmentsSprintgoalsCarryovereverysprintClear anddefinedarchitectureTestingleft to theend of thesprintA lot of/afewmeetingsClarity intickets inJIRAAdd newtasks to thecurrent sprintafterplanningGoogleerrorsPlanningeveryiterationOvercommittingorunderestimatingUnexpectedissuesDefinition ofDone/Acceptancecriteria is inplaceCleardeadlinesDependenciesonstakeholdersor otherteamsScrumsceremoniesBacklogvisibility /nextsprintsUse ofthe slackchannelEffectivecommunicationCompromise ofquality due tothe deadlines,scope andresourcesBusinessexpectationsare clear?Effectivenessin teamdeliverablesEffectiveestimationNeed torethinkfew waysof workingAccess toenvironmentsSprintgoalsCarryovereverysprintClear anddefinedarchitectureTestingleft to theend of thesprintA lot of/afewmeetingsClarity intickets inJIRAAdd newtasks to thecurrent sprintafterplanningGoogleerrorsPlanningeveryiterationOvercommittingorunderestimatingUnexpectedissuesDefinition ofDone/Acceptancecriteria is inplaceCleardeadlinesDependenciesonstakeholdersor otherteamsScrumsceremonies

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