Screenshotor mockupis missingor unclearQA raiseda testabilityconcernearlyRefinementled to storysplitting orcleanupDuplicatefunctionalityexistsWe’vealreadydiscussedthis before…StoryinvolvesexternalteamdependencyRetro itemraisedduringrefinementDev, QA,and POaligned wellon storyscopeLabeling/tagginginconsistent ormissingAcceptancecriteriacopied froma templatewith no editsTitle is toovague orgeneric  No links torelatedJira/Ticket/DesignStory hascarry-overfrom 2+sprints agoA backloggrooming taskwas createdduring thesessionStorycontainsplaceholdertextPeer devsdisagreedonapproachStory islow valuebut higheffortIcebreakermadesomeonesmileStorymarked“ready” butclearly isn’tPO says,“Let me getback to youon that”Story lacks aclear “why”or businessvalueSomeonecalled outmissingDefinition ofReadySomeonejoined lateor missedcontextPotentialregressionriskidentifiedScreenshotor mockupis missingor unclearQA raiseda testabilityconcernearlyRefinementled to storysplitting orcleanupDuplicatefunctionalityexistsWe’vealreadydiscussedthis before…StoryinvolvesexternalteamdependencyRetro itemraisedduringrefinementDev, QA,and POaligned wellon storyscopeLabeling/tagginginconsistent ormissingAcceptancecriteriacopied froma templatewith no editsTitle is toovague orgeneric  No links torelatedJira/Ticket/DesignStory hascarry-overfrom 2+sprints agoA backloggrooming taskwas createdduring thesessionStorycontainsplaceholdertextPeer devsdisagreedonapproachStory islow valuebut higheffortIcebreakermadesomeonesmileStorymarked“ready” butclearly isn’tPO says,“Let me getback to youon that”Story lacks aclear “why”or businessvalueSomeonecalled outmissingDefinition ofReadySomeonejoined lateor missedcontextPotentialregressionriskidentified

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