During sprint,no discussionofprogresstowardsprint goalEng doesnot provideinput into thesprint goalSprint goal oftennot connected toidea of deliveringdemoable usersoftware by sprintend Sprint goalovershadowedby urgent butnon goal-essential workSprint goalnot relatedto ProductobjectiveGoal isvague ornotmeasurableSprint goalis unrealisticgivencapacityWork-in-progress neverdeprioritized tomeet sprintgoalSome teammembersdon't know (orask) what thesprint goal isTeam doesnot prioritizesprint workbased on thesprint goalMultiplesprintgoals inone sprintNodiscussion oftradeoffsto meetsprint goalGoal reflectsindividualpriorities vsProductvisionTeam doesnot celebrateachievingthe goalSprintgoalchangesmid-sprintTeam makesno distinctionbetween finishingwork in progressand meeting thesprint goalSprint goalachieved butno CUSTOMERVALUE isdeliveredBacklogitemscompletedbut goal notachievedSprint goalunlikely to bemet due toexternaldependenciesGoal is notdeprioritized,even whenthere's no hopeof achieving itTeamcommits togoal withoutconfidence itis feasibleTeam doesnot questionrelevance orfeasibility ofsprint goalSprint goalachieved butstakeholdersnot satisfiedTeam feelspressure toachieve goalat expenseof qualityDuring sprint,no discussionofprogresstowardsprint goalEng doesnot provideinput into thesprint goalSprint goal oftennot connected toidea of deliveringdemoable usersoftware by sprintend Sprint goalovershadowedby urgent butnon goal-essential workSprint goalnot relatedto ProductobjectiveGoal isvague ornotmeasurableSprint goalis unrealisticgivencapacityWork-in-progress neverdeprioritized tomeet sprintgoalSome teammembersdon't know (orask) what thesprint goal isTeam doesnot prioritizesprint workbased on thesprint goalMultiplesprintgoals inone sprintNodiscussion oftradeoffsto meetsprint goalGoal reflectsindividualpriorities vsProductvisionTeam doesnot celebrateachievingthe goalSprintgoalchangesmid-sprintTeam makesno distinctionbetween finishingwork in progressand meeting thesprint goalSprint goalachieved butno CUSTOMERVALUE isdeliveredBacklogitemscompletedbut goal notachievedSprint goalunlikely to bemet due toexternaldependenciesGoal is notdeprioritized,even whenthere's no hopeof achieving itTeamcommits togoal withoutconfidence itis feasibleTeam doesnot questionrelevance orfeasibility ofsprint goalSprint goalachieved butstakeholdersnot satisfiedTeam feelspressure toachieve goalat expenseof quality

Sprint-Goal-Challenges 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. During sprint, no discussion of progress toward sprint goal
  2. Eng does not provide input into the sprint goal
  3. Sprint goal often not connected to idea of delivering demoable user software by sprint end
  4. Sprint goal overshadowed by urgent but non goal-essential work
  5. Sprint goal not related to Product objective
  6. Goal is vague or not measurable
  7. Sprint goal is unrealistic given capacity
  8. Work-in-progress never deprioritized to meet sprint goal
  9. Some team members don't know (or ask) what the sprint goal is
  10. Team does not prioritize sprint work based on the sprint goal
  11. Multiple sprint goals in one sprint
  12. No discussion of tradeoffs to meet sprint goal
  13. Goal reflects individual priorities vs Product vision
  14. Team does not celebrate achieving the goal
  15. Sprint goal changes mid-sprint
  16. Team makes no distinction between finishing work in progress and meeting the sprint goal
  17. Sprint goal achieved but no CUSTOMER VALUE is delivered
  18. Backlog items completed but goal not achieved
  19. Sprint goal unlikely to be met due to external dependencies
  20. Goal is not deprioritized, even when there's no hope of achieving it
  21. Team commits to goal without confidence it is feasible
  22. Team does not question relevance or feasibility of sprint goal
  23. Sprint goal achieved but stakeholders not satisfied
  24. Team feels pressure to achieve goal at expense of quality