(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
Developers avoid discussing blockers
to appear productive.
Team commits to more work than they can realistically complete.
Team presents the Increment to
stakeholders in Sprint Review.
Sprint Review is skipped and stakeholders never see the Increment.
Scrum master ignore impediments
reported by the team.
SM coaches the team and facilitates events without dictating work.
Daily Scrum lasts 45 minutes because SM talks too much.
Team identifies one actionable improvement for next Sprint.
Developers collaborate to
split a large backlog item into smaller tasks.
PO ignores team questions about backlog priorities.
PO changes priorities mid-Sprint without team discussion.
Daily Scrum focuses on Sprint Goal progress, not individual status updates.
Scrum Master assigns tasks to developers.
Team skips Retrospective
to save time.
Team collaborates to clarify backlog items during refinement.
Stakeholders provide feedback in Sprint Review that updates the Product Backlog.
Team retro focuses on blaming individuals.
SM assigns
specific tasks to developers during Daily Scrum.
Retrospective results in actionable improvement items.
Team discusses backlog items to commit in Sprint Planning.
Dev Team estimates backlog items together in Planning.
Team skips Daily Scrum because everyone is “too busy.”
Developers report blockers and ask for help in Daily Scrum.
SM facilitates a timeboxed Sprint Planning, keeping discussion focused.
