IcebreakermadesomeonesmileWe’vealreadydiscussedthis before…Acceptancecriteriacopied froma templatewith no editsNo links torelatedJira/Ticket/DesignPO says,“Let me getback to youon that”DuplicatefunctionalityexistsDev, QA,and POaligned wellon storyscopeLabeling/tagginginconsistent ormissingStory hascarry-overfrom 2+sprints agoA backloggrooming taskwas createdduring thesessionRetro itemraisedduringrefinementStory islow valuebut higheffortTitle is toovague orgeneric  Peer devsdisagreedonapproachPotentialregressionriskidentifiedQA raiseda testabilityconcernearlyStoryinvolvesexternalteamdependencySomeonecalled outmissingDefinition ofReadyStorymarked“ready” butclearly isn’tStory lacks aclear “why”or businessvalueStorycontainsplaceholdertextSomeonejoined lateor missedcontextScreenshotor mockupis missingor unclearRefinementled to storysplitting orcleanupIcebreakermadesomeonesmileWe’vealreadydiscussedthis before…Acceptancecriteriacopied froma templatewith no editsNo links torelatedJira/Ticket/DesignPO says,“Let me getback to youon that”DuplicatefunctionalityexistsDev, QA,and POaligned wellon storyscopeLabeling/tagginginconsistent ormissingStory hascarry-overfrom 2+sprints agoA backloggrooming taskwas createdduring thesessionRetro itemraisedduringrefinementStory islow valuebut higheffortTitle is toovague orgeneric  Peer devsdisagreedonapproachPotentialregressionriskidentifiedQA raiseda testabilityconcernearlyStoryinvolvesexternalteamdependencySomeonecalled outmissingDefinition ofReadyStorymarked“ready” butclearly isn’tStory lacks aclear “why”or businessvalueStorycontainsplaceholdertextSomeonejoined lateor missedcontextScreenshotor mockupis missingor unclearRefinementled to storysplitting orcleanup

Untitled 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. Icebreaker made someone smile
  2. We’ve already discussed this before…
  3. Acceptance criteria copied from a template with no edits
  4. No links to related Jira/Ticket/Design
  5. PO says, “Let me get back to you on that”
  6. Duplicate functionality exists
  7. Dev, QA, and PO aligned well on story scope
  8. Labeling/tagging inconsistent or missing
  9. Story has carry-over from 2+ sprints ago
  10. A backlog grooming task was created during the session
  11. Retro item raised during refinement
  12. Story is low value but high effort
  13. Title is too vague or generic
  14. Peer devs disagreed on approach
  15. Potential regression risk identified
  16. QA raised a testability concern early
  17. Story involves external team dependency
  18. Someone called out missing Definition of Ready
  19. Story marked “ready” but clearly isn’t
  20. Story lacks a clear “why” or business value
  21. Story contains placeholder text
  22. Someone joined late or missed context
  23. Screenshot or mockup is missing or unclear
  24. Refinement led to story splitting or cleanup