Clarity intickets inJIRADependenciesonstakeholdersor otherteamsBusinessexpectationsare clear?PlanningeveryiterationNeed torethinkfew waysof workingSprintgoalsAccess toenvironmentsAdd newtasks to thecurrent sprintafterplanningDefinition ofDone/Acceptancecriteria is inplaceScrumsceremoniesBacklogvisibility /nextsprintsCleardeadlinesA lot of/afewmeetingsEffectivecommunicationEffectiveestimationOvercommittingorunderestimatingEffectivenessin teamdeliverablesTestingleft to theend of thesprintCarryovereverysprintGoogleerrorsUnexpectedissuesCompromise ofquality due tothe deadlines,scope andresourcesUse ofthe slackchannelClear anddefinedarchitectureClarity intickets inJIRADependenciesonstakeholdersor otherteamsBusinessexpectationsare clear?PlanningeveryiterationNeed torethinkfew waysof workingSprintgoalsAccess toenvironmentsAdd newtasks to thecurrent sprintafterplanningDefinition ofDone/Acceptancecriteria is inplaceScrumsceremoniesBacklogvisibility /nextsprintsCleardeadlinesA lot of/afewmeetingsEffectivecommunicationEffectiveestimationOvercommittingorunderestimatingEffectivenessin teamdeliverablesTestingleft to theend of thesprintCarryovereverysprintGoogleerrorsUnexpectedissuesCompromise ofquality due tothe deadlines,scope andresourcesUse ofthe slackchannelClear anddefinedarchitecture

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