Labeling/tagginginconsistent ormissingStory islow valuebut higheffortIcebreakermadesomeonesmileRetro itemraisedduringrefinementNo links torelatedJira/Ticket/DesignAcceptancecriteriacopied froma templatewith no editsDev, QA,and POaligned wellon storyscopeA backloggrooming taskwas createdduring thesessionStorycontainsplaceholdertextTitle is toovague orgeneric  Someonejoined lateor missedcontextStory hascarry-overfrom 2+sprints agoDuplicatefunctionalityexistsStory lacks aclear “why”or businessvaluePotentialregressionriskidentifiedPeer devsdisagreedonapproachSomeonecalled outmissingDefinition ofReadyStorymarked“ready” butclearly isn’tStoryinvolvesexternalteamdependencyRefinementled to storysplitting orcleanupScreenshotor mockupis missingor unclearWe’vealreadydiscussedthis before…QA raiseda testabilityconcernearlyPO says,“Let me getback to youon that”Labeling/tagginginconsistent ormissingStory islow valuebut higheffortIcebreakermadesomeonesmileRetro itemraisedduringrefinementNo links torelatedJira/Ticket/DesignAcceptancecriteriacopied froma templatewith no editsDev, QA,and POaligned wellon storyscopeA backloggrooming taskwas createdduring thesessionStorycontainsplaceholdertextTitle is toovague orgeneric  Someonejoined lateor missedcontextStory hascarry-overfrom 2+sprints agoDuplicatefunctionalityexistsStory lacks aclear “why”or businessvaluePotentialregressionriskidentifiedPeer devsdisagreedonapproachSomeonecalled outmissingDefinition ofReadyStorymarked“ready” butclearly isn’tStoryinvolvesexternalteamdependencyRefinementled to storysplitting orcleanupScreenshotor mockupis missingor unclearWe’vealreadydiscussedthis before…QA raiseda testabilityconcernearlyPO says,“Let me getback to youon that”

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