Deliveringbusinessvalue is notpossible mostof the timeTeam feelscomplacent;does notactively seekto improveMeaning of"businessvalue" iscloudyTeam membersare assignedwork andevaluated basedon individualtask completionSprint goals areset without inputfrom thedevelopmentteam, leading tounrealistic targetsTeam membersare more focusedon completingindividual tasksvs meeting sprintgoalTeam isfocused ondeliveringbusiness valueeach sprintProgresstoward thesprint goal isnotdiscussedSprint goalseemsarbitraryor vagueOne teammember'sabsence stronglyimpacts theteam's ability tomake decisionsSprint goal is notused as a guidefor decisionmaking and sprintback prioritizationduring sprintSprint goalreflects astep towarda largerproduct goalTeam avoidsconflict ordisagreementProduct anddev teamcollaborate torefine andprioritizebacklogRetro resultsin ongoingimprovementTeam omitsto celebratewhenmilestonesare achievedTeam onlyspeaks tostakeholdersthru Product orScrum masterMeaning ofterm"businessvalue" isclearTeam worksdirectly withbusinessstakeholderswheneverpossibleTeamcelebratesmeeting sprintgoal or othermilestonesLack ofclarity onproject visioncausesconfusionSprint goalsare notrelated todemo-ablesoftwareOwnership andresponsibility isnot shared evenlyamong teammembers, leadingto bottlenecksWhen a specificmember of theteam proposesan idea, othershesitate tochallenge itDeliveringbusinessvalue is notpossible mostof the timeTeam feelscomplacent;does notactively seekto improveMeaning of"businessvalue" iscloudyTeam membersare assignedwork andevaluated basedon individualtask completionSprint goals areset without inputfrom thedevelopmentteam, leading tounrealistic targetsTeam membersare more focusedon completingindividual tasksvs meeting sprintgoalTeam isfocused ondeliveringbusiness valueeach sprintProgresstoward thesprint goal isnotdiscussedSprint goalseemsarbitraryor vagueOne teammember'sabsence stronglyimpacts theteam's ability tomake decisionsSprint goal is notused as a guidefor decisionmaking and sprintback prioritizationduring sprintSprint goalreflects astep towarda largerproduct goalTeam avoidsconflict ordisagreementProduct anddev teamcollaborate torefine andprioritizebacklogRetro resultsin ongoingimprovementTeam omitsto celebratewhenmilestonesare achievedTeam onlyspeaks tostakeholdersthru Product orScrum masterMeaning ofterm"businessvalue" isclearTeam worksdirectly withbusinessstakeholderswheneverpossibleTeamcelebratesmeeting sprintgoal or othermilestonesLack ofclarity onproject visioncausesconfusionSprint goalsare notrelated todemo-ablesoftwareOwnership andresponsibility isnot shared evenlyamong teammembers, leadingto bottlenecksWhen a specificmember of theteam proposesan idea, othershesitate tochallenge it

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