FollowingJIRAworkflowprocessEffectivenessin teamdeliverablesEffectiveestimationAdd newtasks to thecurrent sprintafterplanningEffectivecommunicationA lot of/afewmeetingsScrumsceremoniesCleardeadlinesUnexpectedissuesClarity intickets inJIRASuccess!Backlogvisibility /nextsprintsUse ofthe slackchannelTestingleft to theend of thesprintCompromise ofquality due tothe deadlines,scope andresourcesBusinessexpectationsare clear?Clear anddefinedarchitectureCarryovereverysprintDefinition ofDone/Acceptancecriteria is inplaceOvercommittingorunderestimatingAccess toenvironmentsPlanningeveryiterationSprintgoalsNeed torethinkfew waysof workingDependenciesonstakeholdersor otherteamsFollowingJIRAworkflowprocessEffectivenessin teamdeliverablesEffectiveestimationAdd newtasks to thecurrent sprintafterplanningEffectivecommunicationA lot of/afewmeetingsScrumsceremoniesCleardeadlinesUnexpectedissuesClarity intickets inJIRASuccess!Backlogvisibility /nextsprintsUse ofthe slackchannelTestingleft to theend of thesprintCompromise ofquality due tothe deadlines,scope andresourcesBusinessexpectationsare clear?Clear anddefinedarchitectureCarryovereverysprintDefinition ofDone/Acceptancecriteria is inplaceOvercommittingorunderestimatingAccess toenvironmentsPlanningeveryiterationSprintgoalsNeed torethinkfew waysof workingDependenciesonstakeholdersor otherteams

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