Story lacks aclear “why”or businessvalueDev, QA,and POaligned wellon storyscopeStory islow valuebut higheffortStory hascarry-overfrom 2+sprints agoRefinementled to storysplitting orcleanupQA raiseda testabilityconcernearlyA backloggrooming taskwas createdduring thesessionStoryinvolvesexternalteamdependencyAcceptancecriteriacopied froma templatewith no editsIcebreakermadesomeonesmileLabeling/tagginginconsistent ormissingPO says,“Let me getback to youon that”PotentialregressionriskidentifiedWe’vealreadydiscussedthis before…Storymarked“ready” butclearly isn’tSomeonejoined lateor missedcontextRetro itemraisedduringrefinementSomeonecalled outmissingDefinition ofReadyPeer devsdisagreedonapproachScreenshotor mockupis missingor unclearStorycontainsplaceholdertextNo links torelatedJira/Ticket/DesignDuplicatefunctionalityexistsTitle is toovague orgeneric  Story lacks aclear “why”or businessvalueDev, QA,and POaligned wellon storyscopeStory islow valuebut higheffortStory hascarry-overfrom 2+sprints agoRefinementled to storysplitting orcleanupQA raiseda testabilityconcernearlyA backloggrooming taskwas createdduring thesessionStoryinvolvesexternalteamdependencyAcceptancecriteriacopied froma templatewith no editsIcebreakermadesomeonesmileLabeling/tagginginconsistent ormissingPO says,“Let me getback to youon that”PotentialregressionriskidentifiedWe’vealreadydiscussedthis before…Storymarked“ready” butclearly isn’tSomeonejoined lateor missedcontextRetro itemraisedduringrefinementSomeonecalled outmissingDefinition ofReadyPeer devsdisagreedonapproachScreenshotor mockupis missingor unclearStorycontainsplaceholdertextNo links torelatedJira/Ticket/DesignDuplicatefunctionalityexistsTitle is toovague orgeneric  

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