Team onlyspeaks tostakeholdersthru Product orScrum masterTeam membersare assignedwork andevaluated basedon individualtask completionTeam omitsto celebratewhenmilestonesare achievedSprint goals areset without inputfrom thedevelopmentteam, leading tounrealistic targetsMeaning ofterm"businessvalue" isclearTeamcelebratesmeeting sprintgoal or othermilestonesTeam isfocused ondeliveringbusiness valueeach sprintWhen a specificmember of theteam proposesan idea, othershesitate tochallenge itOwnership andresponsibility isnot shared evenlyamong teammembers, leadingto bottlenecksTeam worksdirectly withbusinessstakeholderswheneverpossibleMeaning of"businessvalue" iscloudyDeliveringbusinessvalue is notpossible mostof the timeSprint goalsare notrelated todemo-ablesoftwareSprint goalreflects astep towarda largerproduct goalOne teammember'sabsence stronglyimpacts theteam's ability tomake decisionsSprint goal is notused as a guidefor decisionmaking and sprintback prioritizationduring sprintLack ofclarity onproject visioncausesconfusionTeam membersare more focusedon completingindividual tasksvs meeting sprintgoalProduct anddev teamcollaborate torefine andprioritizebacklogProgresstoward thesprint goal isnotdiscussedRetro resultsin ongoingimprovementTeam feelscomplacent;does notactively seekto improveTeam avoidsconflict ordisagreementSprint goalseemsarbitraryor vagueTeam onlyspeaks tostakeholdersthru Product orScrum masterTeam membersare assignedwork andevaluated basedon individualtask completionTeam omitsto celebratewhenmilestonesare achievedSprint goals areset without inputfrom thedevelopmentteam, leading tounrealistic targetsMeaning ofterm"businessvalue" isclearTeamcelebratesmeeting sprintgoal or othermilestonesTeam isfocused ondeliveringbusiness valueeach sprintWhen a specificmember of theteam proposesan idea, othershesitate tochallenge itOwnership andresponsibility isnot shared evenlyamong teammembers, leadingto bottlenecksTeam worksdirectly withbusinessstakeholderswheneverpossibleMeaning of"businessvalue" iscloudyDeliveringbusinessvalue is notpossible mostof the timeSprint goalsare notrelated todemo-ablesoftwareSprint goalreflects astep towarda largerproduct goalOne teammember'sabsence stronglyimpacts theteam's ability tomake decisionsSprint goal is notused as a guidefor decisionmaking and sprintback prioritizationduring sprintLack ofclarity onproject visioncausesconfusionTeam membersare more focusedon completingindividual tasksvs meeting sprintgoalProduct anddev teamcollaborate torefine andprioritizebacklogProgresstoward thesprint goal isnotdiscussedRetro resultsin ongoingimprovementTeam feelscomplacent;does notactively seekto improveTeam avoidsconflict ordisagreementSprint goalseemsarbitraryor vague

Scrum-Boss Bingo! - Call List

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