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