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