A rule orhookstopped amistakeClarity intickets inJIRAEffectivecommunicationEffectivenessin teamdeliverablesScrumsceremoniesA skill didnot triggerwhen itshouldPlanningeveryiterationCompromise ofquality due tothe deadlines,scope andresourcesAgentchangedthe test, notthe codeSprintgoalsWorktreesaved amessymergeAgent PRneededno reviewchangesNeed torethinkfew waysof workingEffectiveestimationUse ofthe slackchannelAgentexplainedlegacycode wellBusinessexpectationsare clear?Contextor tokenblowupDependenciesonstakeholdersor otherteamsAgentcommittedto trunkCleardeadlinesBacklogvisibility /nextsprintsDefinition ofDone/Acceptancecriteria is inplaceCarryovereverysprintAgentignoredAGENTS.mdFailing testreproducedthe bugClear anddefinedarchitectureWrongagentpicked forthe taskA skillsaved mereal timeA memoryrecall paidoffUnexpectedissuesStalememorymisled theagentFollowingJIRAworkflowprocessPermissionpromptsslowed medownAgentnailed itfirst timeAdd newtasks to thecurrent sprintafterplanningFound anew usefor anagentAccess toenvironmentsAdversarialreviewcaught areal bugGraph orreckoneransweredbefore grepSuccess!Agent over-engineereda smallchangeAgentchangedmore thanI askedHallucinatedan endpointor fieldAgent skippedrenewal,clone ormigrationimpactOvercommittingorunderestimatingSubagentbeatdoing itinlineA lot of/afewmeetingsTestingleft to theend of thesprintA rule orhookstopped amistakeClarity intickets inJIRAEffectivecommunicationEffectivenessin teamdeliverablesScrumsceremoniesA skill didnot triggerwhen itshouldPlanningeveryiterationCompromise ofquality due tothe deadlines,scope andresourcesAgentchangedthe test, notthe codeSprintgoalsWorktreesaved amessymergeAgent PRneededno reviewchangesNeed torethinkfew waysof workingEffectiveestimationUse ofthe slackchannelAgentexplainedlegacycode wellBusinessexpectationsare clear?Contextor tokenblowupDependenciesonstakeholdersor otherteamsAgentcommittedto trunkCleardeadlinesBacklogvisibility /nextsprintsDefinition ofDone/Acceptancecriteria is inplaceCarryovereverysprintAgentignoredAGENTS.mdFailing testreproducedthe bugClear anddefinedarchitectureWrongagentpicked forthe taskA skillsaved mereal timeA memoryrecall paidoffUnexpectedissuesStalememorymisled theagentFollowingJIRAworkflowprocessPermissionpromptsslowed medownAgentnailed itfirst timeAdd newtasks to thecurrent sprintafterplanningFound anew usefor anagentAccess toenvironmentsAdversarialreviewcaught areal bugGraph orreckoneransweredbefore grepSuccess!Agent over-engineereda smallchangeAgentchangedmore thanI askedHallucinatedan endpointor fieldAgent skippedrenewal,clone ormigrationimpactOvercommittingorunderestimatingSubagentbeatdoing itinlineA lot of/afewmeetingsTestingleft to theend of thesprint

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
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
  1. A rule or hook stopped a mistake
  2. Clarity in tickets in JIRA
  3. Effective communication
  4. Effectiveness in team deliverables
  5. Scrums ceremonies
  6. A skill did not trigger when it should
  7. Planning every iteration
  8. Compromise of quality due to the deadlines, scope and resources
  9. Agent changed the test, not the code
  10. Sprint goals
  11. Worktree saved a messy merge
  12. Agent PR needed no review changes
  13. Need to rethink few ways of working
  14. Effective estimation
  15. Use of the slack channel
  16. Agent explained legacy code well
  17. Business expectations are clear?
  18. Context or token blowup
  19. Dependencies on stakeholders or other teams
  20. Agent committed to trunk
  21. Clear deadlines
  22. Backlog visibility / next sprints
  23. Definition of Done/ Acceptance criteria is in place
  24. Carry over every sprint
  25. Agent ignored AGENTS.md
  26. Failing test reproduced the bug
  27. Clear and defined architecture
  28. Wrong agent picked for the task
  29. A skill saved me real time
  30. A memory recall paid off
  31. Unexpected issues
  32. Stale memory misled the agent
  33. Following JIRA workflow process
  34. Permission prompts slowed me down
  35. Agent nailed it first time
  36. Add new tasks to the current sprint after planning
  37. Found a new use for an agent
  38. Access to environments
  39. Adversarial review caught a real bug
  40. Graph or reckoner answered before grep
  41. Success!
  42. Agent over-engineered a small change
  43. Agent changed more than I asked
  44. Hallucinated an endpoint or field
  45. Agent skipped renewal, clone or migration impact
  46. Overcommitting or underestimating
  47. Subagent beat doing it inline
  48. A lot of/a few meetings
  49. Testing left to the end of the sprint