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