(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
Team strategizes to deliver business value each sprint
Team speaks to stakeholders only thru Product or Scrum Master
Sprint goals not related to demo-able software
Ownership or responsibility not evenly shared; leads to bottlenecks
Sprint goal reflects a step toward a larger product goal
Team members assigned work and evaluated based on individual task completion
Progress toward the sprint goal is not discussed
Product and Eng collaborate to refine and prioritize Produt backlog
Sprint goal seems arbitrary or vague
Meaning of business value is clear
Delivering business value not possible most of the time
Team works directly with business stakeholders whenever possible
Team celebrates meeting sprint goals or other milestones
Sprint goals set w/o input from dev team, leading to unrealistic targets
Team culture is to avoid disagreement or ignore conflict
Lack of clarity on project direction causes confusion
Team members focused on completing individual tasks vs achieving sprint goal
Team feels there's nothing else to improve on
If one person is absent the team's ability to make decisions is strongly impacted
When a specific team member proposes an idea, others hesitate to challenge it
The meaning of "business value" is cloudy
Retro results in ongoing improvement
Sprint goal not used to guide decision making and prioritization during sprint
Retros include discussion but no improvement action/follow up
