Developerscollaborate tosplit a largebacklog iteminto smallertasks.Teamdiscussesbacklog itemsto commit inSprint Planning.Developersavoiddiscussingblockersto appearproductive.SM facilitates atimeboxedSprint Planning,keepingdiscussionfocused.Teamcollaborates toclarify backlogitems duringrefinement.Team presentsthe Incrementtostakeholders inSprint Review.Developersreportblockers andask for help inDaily Scrum.PO ignoresteamquestionsabout backlogpriorities.Team commitsto more workthan they canrealisticallycomplete.PO changesprioritiesmid-Sprintwithout teamdiscussion.Team retrofocuses onblamingindividuals.ScrumMasterassignstasks todevelopers.Retrospectiveresults inactionableimprovementitems.Sprint Reviewis skipped andstakeholdersnever see theIncrement.SM assignsspecific tasksto developersduring DailyScrum.Dev Teamestimatesbacklog itemstogether inPlanning.Daily Scrumlasts 45minutesbecause SMtalks too much.Team identifiesone actionableimprovementfor next Sprint.Stakeholdersprovide feedbackin Sprint Reviewthat updates theProduct Backlog.Team skipsRetrospectiveto save time.SM coachesthe team andfacilitatesevents withoutdictating work.Scrummaster ignoreimpedimentsreported bythe team.Team skipsDaily Scrumbecauseeveryone is“too busy.”Daily Scrumfocuses onSprint Goalprogress, notindividualstatus updates.Developerscollaborate tosplit a largebacklog iteminto smallertasks.Teamdiscussesbacklog itemsto commit inSprint Planning.Developersavoiddiscussingblockersto appearproductive.SM facilitates atimeboxedSprint Planning,keepingdiscussionfocused.Teamcollaborates toclarify backlogitems duringrefinement.Team presentsthe Incrementtostakeholders inSprint Review.Developersreportblockers andask for help inDaily Scrum.PO ignoresteamquestionsabout backlogpriorities.Team commitsto more workthan they canrealisticallycomplete.PO changesprioritiesmid-Sprintwithout teamdiscussion.Team retrofocuses onblamingindividuals.ScrumMasterassignstasks todevelopers.Retrospectiveresults inactionableimprovementitems.Sprint Reviewis skipped andstakeholdersnever see theIncrement.SM assignsspecific tasksto developersduring DailyScrum.Dev Teamestimatesbacklog itemstogether inPlanning.Daily Scrumlasts 45minutesbecause SMtalks too much.Team identifiesone actionableimprovementfor next Sprint.Stakeholdersprovide feedbackin Sprint Reviewthat updates theProduct Backlog.Team skipsRetrospectiveto save time.SM coachesthe team andfacilitatesevents withoutdictating work.Scrummaster ignoreimpedimentsreported bythe team.Team skipsDaily Scrumbecauseeveryone is“too busy.”Daily Scrumfocuses onSprint Goalprogress, notindividualstatus updates.

Scrum or Anti-Scrum - 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. Developers collaborate to split a large backlog item into smaller tasks.
  2. Team discusses backlog items to commit in Sprint Planning.
  3. Developers avoid discussing blockers to appear productive.
  4. SM facilitates a timeboxed Sprint Planning, keeping discussion focused.
  5. Team collaborates to clarify backlog items during refinement.
  6. Team presents the Increment to stakeholders in Sprint Review.
  7. Developers report blockers and ask for help in Daily Scrum.
  8. PO ignores team questions about backlog priorities.
  9. Team commits to more work than they can realistically complete.
  10. PO changes priorities mid-Sprint without team discussion.
  11. Team retro focuses on blaming individuals.
  12. Scrum Master assigns tasks to developers.
  13. Retrospective results in actionable improvement items.
  14. Sprint Review is skipped and stakeholders never see the Increment.
  15. SM assigns specific tasks to developers during Daily Scrum.
  16. Dev Team estimates backlog items together in Planning.
  17. Daily Scrum lasts 45 minutes because SM talks too much.
  18. Team identifies one actionable improvement for next Sprint.
  19. Stakeholders provide feedback in Sprint Review that updates the Product Backlog.
  20. Team skips Retrospective to save time.
  21. SM coaches the team and facilitates events without dictating work.
  22. Scrum master ignore impediments reported by the team.
  23. Team skips Daily Scrum because everyone is “too busy.”
  24. Daily Scrum focuses on Sprint Goal progress, not individual status updates.