Success!SprintgoalsNeed torethinkfew waysof workingEffectivenessin teamdeliverablesA lot of/afewmeetingsUse ofthe slackchannelOvercommittingorunderestimatingPlanningeveryiterationCompromise ofquality due tothe deadlines,scope andresourcesBacklogvisibility /nextsprintsDependenciesonstakeholdersor otherteamsAdd newtasks to thecurrent sprintafterplanningAccess toenvironmentsEffectivecommunicationBusinessexpectationsare clear?Definition ofDone/Acceptancecriteria is inplaceCleardeadlinesCarryovereverysprintUnexpectedissuesFollowingJIRAworkflowprocessScrumsceremoniesClear anddefinedarchitectureEffectiveestimationTestingleft to theend of thesprintClarity intickets inJIRASuccess!SprintgoalsNeed torethinkfew waysof workingEffectivenessin teamdeliverablesA lot of/afewmeetingsUse ofthe slackchannelOvercommittingorunderestimatingPlanningeveryiterationCompromise ofquality due tothe deadlines,scope andresourcesBacklogvisibility /nextsprintsDependenciesonstakeholdersor otherteamsAdd newtasks to thecurrent sprintafterplanningAccess toenvironmentsEffectivecommunicationBusinessexpectationsare clear?Definition ofDone/Acceptancecriteria is inplaceCleardeadlinesCarryovereverysprintUnexpectedissuesFollowingJIRAworkflowprocessScrumsceremoniesClear anddefinedarchitectureEffectiveestimationTestingleft to theend of thesprintClarity 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
25
  1. Success!
  2. Sprint goals
  3. Need to rethink few ways of working
  4. Effectiveness in team deliverables
  5. A lot of/a few meetings
  6. Use of the slack channel
  7. Overcommitting or underestimating
  8. Planning every iteration
  9. Compromise of quality due to the deadlines, scope and resources
  10. Backlog visibility / next sprints
  11. Dependencies on stakeholders or other teams
  12. Add new tasks to the current sprint after planning
  13. Access to environments
  14. Effective communication
  15. Business expectations are clear?
  16. Definition of Done/ Acceptance criteria is in place
  17. Clear deadlines
  18. Carry over every sprint
  19. Unexpected issues
  20. Following JIRA workflow process
  21. Scrums ceremonies
  22. Clear and defined architecture
  23. Effective estimation
  24. Testing left to the end of the sprint
  25. Clarity in tickets in JIRA