Meaning of"businessvalue" iscloudyProduct anddev teamcollaborate torefine andprioritizebacklogTeam membersare assignedwork andevaluated basedon individualtask completionTeam omitsto celebratewhenmilestonesare achievedOwnership andresponsibility isnot shared evenlyamong teammembers, leadingto bottlenecksSprint goalsare notrelated todemo-ablesoftwareRetro resultsin ongoingimprovementTeam membersare more focusedon completingindividual tasksvs meeting sprintgoalSprint goalreflects astep towarda largerproduct goalSprint goalseemsarbitraryor vagueMeaning ofterm"businessvalue" isclearSprint goal is notused as a guidefor decisionmaking and sprintback prioritizationduring sprintOne teammember'sabsence stronglyimpacts theteam's ability tomake decisionsDeliveringbusinessvalue is notpossible mostof the timeTeam feelscomplacent;does notactively seekto improveSprint goals areset without inputfrom thedevelopmentteam, leading tounrealistic targetsTeam onlyspeaks tostakeholdersthru Product orScrum masterTeam worksdirectly withbusinessstakeholderswheneverpossibleProgresstoward thesprint goal isnotdiscussedWhen a specificmember of theteam proposesan idea, othershesitate tochallenge itTeam avoidsconflict ordisagreementLack ofclarity onproject visioncausesconfusionTeam isfocused ondeliveringbusiness valueeach sprintTeamcelebratesmeeting sprintgoal or othermilestonesMeaning of"businessvalue" iscloudyProduct anddev teamcollaborate torefine andprioritizebacklogTeam membersare assignedwork andevaluated basedon individualtask completionTeam omitsto celebratewhenmilestonesare achievedOwnership andresponsibility isnot shared evenlyamong teammembers, leadingto bottlenecksSprint goalsare notrelated todemo-ablesoftwareRetro resultsin ongoingimprovementTeam membersare more focusedon completingindividual tasksvs meeting sprintgoalSprint goalreflects astep towarda largerproduct goalSprint goalseemsarbitraryor vagueMeaning ofterm"businessvalue" isclearSprint goal is notused as a guidefor decisionmaking and sprintback prioritizationduring sprintOne teammember'sabsence stronglyimpacts theteam's ability tomake decisionsDeliveringbusinessvalue is notpossible mostof the timeTeam feelscomplacent;does notactively seekto improveSprint goals areset without inputfrom thedevelopmentteam, leading tounrealistic targetsTeam onlyspeaks tostakeholdersthru Product orScrum masterTeam worksdirectly withbusinessstakeholderswheneverpossibleProgresstoward thesprint goal isnotdiscussedWhen a specificmember of theteam proposesan idea, othershesitate tochallenge itTeam avoidsconflict ordisagreementLack ofclarity onproject visioncausesconfusionTeam isfocused ondeliveringbusiness valueeach sprintTeamcelebratesmeeting sprintgoal or othermilestones

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