StoryinvolvesexternalteamdependencyPO says,“Let me getback to youon that”No links torelatedJira/Ticket/DesignDev, QA,and POaligned wellon storyscopeLabeling/tagginginconsistent ormissingStorymarked“ready” butclearly isn’tPeer devsdisagreedonapproachScreenshotor mockupis missingor unclearStory hascarry-overfrom 2+sprints agoAcceptancecriteriacopied froma templatewith no editsRetro itemraisedduringrefinementIcebreakermadesomeonesmileWe’vealreadydiscussedthis before…DuplicatefunctionalityexistsPotentialregressionriskidentifiedStory islow valuebut higheffortStory lacks aclear “why”or businessvalueSomeonejoined lateor missedcontextA backloggrooming taskwas createdduring thesessionRefinementled to storysplitting orcleanupTitle is toovague orgeneric  Someonecalled outmissingDefinition ofReadyStorycontainsplaceholdertextQA raiseda testabilityconcernearlyStoryinvolvesexternalteamdependencyPO says,“Let me getback to youon that”No links torelatedJira/Ticket/DesignDev, QA,and POaligned wellon storyscopeLabeling/tagginginconsistent ormissingStorymarked“ready” butclearly isn’tPeer devsdisagreedonapproachScreenshotor mockupis missingor unclearStory hascarry-overfrom 2+sprints agoAcceptancecriteriacopied froma templatewith no editsRetro itemraisedduringrefinementIcebreakermadesomeonesmileWe’vealreadydiscussedthis before…DuplicatefunctionalityexistsPotentialregressionriskidentifiedStory islow valuebut higheffortStory lacks aclear “why”or businessvalueSomeonejoined lateor missedcontextA backloggrooming taskwas createdduring thesessionRefinementled to storysplitting orcleanupTitle is toovague orgeneric  Someonecalled outmissingDefinition ofReadyStorycontainsplaceholdertextQA raiseda testabilityconcernearly

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