Meaning ofterm"businessvalue" isclearTeam membersare more focusedon completingindividual tasksvs meeting sprintgoalProgresstoward thesprint goal isnotdiscussedSprint goals areset without inputfrom thedevelopmentteam, leading tounrealistic targetsTeam isfocused ondeliveringbusiness valueeach sprintOne teammember'sabsence stronglyimpacts theteam's ability tomake decisionsTeam membersare assignedwork andevaluated basedon individualtask completionSprint goal is notused as a guidefor decisionmaking and sprintback prioritizationduring sprintOwnership andresponsibility isnot shared evenlyamong teammembers, leadingto bottlenecksTeam worksdirectly withbusinessstakeholderswheneverpossibleSprint goalsare notrelated todemo-ablesoftwareTeam onlyspeaks tostakeholdersthru Product orScrum masterLack ofclarity onproject visioncausesconfusionProduct anddev teamcollaborate torefine andprioritizebacklogTeam omitsto celebratewhenmilestonesare achievedTeamcelebratesmeeting sprintgoal or othermilestonesRetro resultsin ongoingimprovementTeam avoidsconflict ordisagreementSprint goalreflects astep towarda largerproduct goalDeliveringbusinessvalue is notpossible mostof the timeSprint goalseemsarbitraryor vagueTeam feelscomplacent;does notactively seekto improveMeaning of"businessvalue" iscloudyWhen a specificmember of theteam proposesan idea, othershesitate tochallenge itMeaning ofterm"businessvalue" isclearTeam membersare more focusedon completingindividual tasksvs meeting sprintgoalProgresstoward thesprint goal isnotdiscussedSprint goals areset without inputfrom thedevelopmentteam, leading tounrealistic targetsTeam isfocused ondeliveringbusiness valueeach sprintOne teammember'sabsence stronglyimpacts theteam's ability tomake decisionsTeam membersare assignedwork andevaluated basedon individualtask completionSprint goal is notused as a guidefor decisionmaking and sprintback prioritizationduring sprintOwnership andresponsibility isnot shared evenlyamong teammembers, leadingto bottlenecksTeam worksdirectly withbusinessstakeholderswheneverpossibleSprint goalsare notrelated todemo-ablesoftwareTeam onlyspeaks tostakeholdersthru Product orScrum masterLack ofclarity onproject visioncausesconfusionProduct anddev teamcollaborate torefine andprioritizebacklogTeam omitsto celebratewhenmilestonesare achievedTeamcelebratesmeeting sprintgoal or othermilestonesRetro resultsin ongoingimprovementTeam avoidsconflict ordisagreementSprint goalreflects astep towarda largerproduct goalDeliveringbusinessvalue is notpossible mostof the timeSprint goalseemsarbitraryor vagueTeam feelscomplacent;does notactively seekto improveMeaning of"businessvalue" iscloudyWhen 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. Meaning of term "business value" is clear
  2. Team members are more focused on completing individual tasks vs meeting sprint goal
  3. Progress toward the sprint goal is not discussed
  4. Sprint goals are set without input from the development team, leading to unrealistic targets
  5. Team is focused on delivering business value each sprint
  6. One team member's absence strongly impacts the team's ability to make decisions
  7. Team members are assigned work and evaluated based on individual task completion
  8. Sprint goal is not used as a guide for decision making and sprint back prioritization during sprint
  9. Ownership and responsibility is not shared evenly among team members, leading to bottlenecks
  10. Team works directly with business stakeholders whenever possible
  11. Sprint goals are not related to demo-able software
  12. Team only speaks to stakeholders thru Product or Scrum master
  13. Lack of clarity on project vision causes confusion
  14. Product and dev team collaborate to refine and prioritize backlog
  15. Team omits to celebrate when milestones are achieved
  16. Team celebrates meeting sprint goal or other milestones
  17. Retro results in ongoing improvement
  18. Team avoids conflict or disagreement
  19. Sprint goal reflects a step toward a larger product goal
  20. Delivering business value is not possible most of the time
  21. Sprint goal seems arbitrary or vague
  22. Team feels complacent; does not actively seek to improve
  23. Meaning of "business value" is cloudy
  24. When a specific member of the team proposes an idea, others hesitate to challenge it