CarryovereverysprintGoogleerrorsEffectivecommunicationCompromise ofquality due tothe deadlines,scope andresourcesUnexpectedissuesAdd newtasks to thecurrent sprintafterplanningOvercommittingorunderestimatingDependenciesonstakeholdersor otherteamsTestingleft to theend of thesprintSprintgoalsNeed torethinkfew waysof workingBusinessexpectationsare clear?Clear anddefinedarchitectureDefinition ofDone/Acceptancecriteria is inplaceBacklogvisibility /nextsprintsAccess toenvironmentsCleardeadlinesClarity intickets inJIRAEffectiveestimationScrumsceremoniesA lot of/afewmeetingsEffectivenessin teamdeliverablesUse ofthe slackchannelPlanningeveryiterationCarryovereverysprintGoogleerrorsEffectivecommunicationCompromise ofquality due tothe deadlines,scope andresourcesUnexpectedissuesAdd newtasks to thecurrent sprintafterplanningOvercommittingorunderestimatingDependenciesonstakeholdersor otherteamsTestingleft to theend of thesprintSprintgoalsNeed torethinkfew waysof workingBusinessexpectationsare clear?Clear anddefinedarchitectureDefinition ofDone/Acceptancecriteria is inplaceBacklogvisibility /nextsprintsAccess toenvironmentsCleardeadlinesClarity intickets inJIRAEffectiveestimationScrumsceremoniesA lot of/afewmeetingsEffectivenessin teamdeliverablesUse ofthe slackchannelPlanningeveryiteration

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