This bingo card has a free space and 24 words: Story involves external team dependency, Title is too vague or generic, Story has carry-over from 2+ sprints ago, Someone called out missing Definition of Ready, Story is low value but high effort, Screenshot or mockup is missing or unclear, Story lacks a clear “why” or business value, Peer devs disagreed on approach, Duplicate functionality exists, Retro item raised during refinement, Potential regression risk identified, Story contains placeholder text, PO says, “Let me get back to you on that”, Dev, QA, and PO aligned well on story scope, We’ve already discussed this before…, Acceptance criteria copied from a template with no edits, Labeling/tagging inconsistent or missing, QA raised a testability concern early, Someone joined late or missed context, Story marked “ready” but clearly isn’t, No links to related Jira/Ticket/Design, A backlog grooming task was created during the session, Icebreaker made someone smile and Refinement led to story splitting or cleanup.
retro bingo | MAC QA | Daily Standup Bingo | Beach Trip Bingo | Conference Call Bingo - 5/12
Share this URL with your players:
For more control of your online game, create a clone of this card first.
Learn how to conduct a bingo game.
With players vying for a you'll have to call about __ items before someone wins. There's a __% chance that a lucky player would win after calling __ items.
Tip: If you want your game to last longer (on average), add more unique words/images to it.
