(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
Delivering business value is not possible most of the time
Team feels complacent; does not actively seek to improve
Meaning of "business value" is cloudy
Team members are assigned work and evaluated based on individual task completion
Sprint goals are set without input from the development team, leading to unrealistic targets
Team members are more focused on completing individual tasks vs meeting sprint goal
Team is focused on delivering business value each sprint
Progress toward the sprint goal is not discussed
Sprint goal seems arbitrary or vague
One team member's absence strongly impacts the team's ability to make decisions
Sprint goal is not used as a guide for decision making and sprint back prioritization during sprint
Sprint goal reflects a step toward a larger product goal
Team avoids conflict or disagreement
Product and dev team collaborate to refine and prioritize backlog
Retro results in ongoing improvement
Team omits to celebrate when milestones are achieved
Team only speaks to stakeholders thru Product or Scrum master
Meaning of term "business value" is clear
Team works directly with business stakeholders whenever possible
Team celebrates meeting sprint goal or other milestones
Lack of clarity on project vision causes confusion
Sprint goals are not related to demo-able software
Ownership and responsibility is not shared evenly among team members, leading to bottlenecks
When a specific member of the team proposes an idea, others hesitate to challenge it
