Add newtasks to thecurrent sprintafterplanningCleardeadlinesDefinition ofDone/Acceptancecriteria is inplaceUnexpectedissuesScrumsceremoniesOvercommittingorunderestimatingTestingleft to theend of thesprintBacklogvisibility /nextsprintsCarryovereverysprintClear anddefinedarchitectureEffectivenessin teamdeliverablesPlanningeveryiterationA lot of/afewmeetingsEffectivecommunicationUse ofthe slackchannelSprintgoalsGoogleerrorsCompromise ofquality due tothe deadlines,scope andresourcesEffectiveestimationAccess toenvironmentsDependenciesonstakeholdersor otherteamsBusinessexpectationsare clear?Need torethinkfew waysof workingClarity intickets inJIRAAdd newtasks to thecurrent sprintafterplanningCleardeadlinesDefinition ofDone/Acceptancecriteria is inplaceUnexpectedissuesScrumsceremoniesOvercommittingorunderestimatingTestingleft to theend of thesprintBacklogvisibility /nextsprintsCarryovereverysprintClear anddefinedarchitectureEffectivenessin teamdeliverablesPlanningeveryiterationA lot of/afewmeetingsEffectivecommunicationUse ofthe slackchannelSprintgoalsGoogleerrorsCompromise ofquality due tothe deadlines,scope andresourcesEffectiveestimationAccess toenvironmentsDependenciesonstakeholdersor otherteamsBusinessexpectationsare clear?Need torethinkfew waysof workingClarity intickets inJIRA

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