Hasexperienced“water-Scrum-fall”Has witnessed ateam commit toway more workthan they couldrealisticallycomplete in asprintLoves orhates JirapassionatelyHas been on ateam thatmonitored cycletime andactively tried todecrease itHas workedon a fullycollocatedAgile teamHas done afunretrospectiveformatHas workedwith a trulyamazingProductOwnerHas seen ateam strugglewith too manypriorities atonceHas beenpart of ateam thatchanged howthey estimateHas donemob or pairprogrammingHas seen ateam gofrom chaosto highperformanceHas workedin an orgwhere Agilewas “only forengineering"Has witnessedan epic debateover storypoints vs. timeestimatesHasworked ona KanbanteamHas had toexplain that“Scrum” and“Agile” are notthe same thingHas had astakeholderdemand adeadlinewithout contextHas tried anew Agileframework(SAFe,LeSS, etc.)Has been ina standupthat lastedover 30minutesHas seen anAgiletransformationstruggleHas arguedabout whatDefinition ofReady or Doneshould includeHas workedwith a team thatonly did Agileceremonies butdidn’t embraceAgile valuesHas coacheda teamthrough theirfirstretrospectiveHas been partof anexperiment thattotally failed—but learned alot!Has seen aProduct Owneract as a projectmanager insteadof a value-drivenleaderHas run aretro thatwent offthe railsHas heard“We’re Agile, sowe don’t needdocumentation”Has beenpart of anun-conferenceHas workedon a teamwith nodedicatedScrum MasterHas hadto defendWIP limitsHas been ona team thatabandonedstandupsHasparticipatedin a LeanCoffeesessionHas taughtsomeoneabout AgileHas beentold Agiledoesn’t workin “ourspace/team”Has seen ateam self-organize in apowerful wayHasexperienced“water-Scrum-fall”Has witnessed ateam commit toway more workthan they couldrealisticallycomplete in asprintLoves orhates JirapassionatelyHas been on ateam thatmonitored cycletime andactively tried todecrease itHas workedon a fullycollocatedAgile teamHas done afunretrospectiveformatHas workedwith a trulyamazingProductOwnerHas seen ateam strugglewith too manypriorities atonceHas beenpart of ateam thatchanged howthey estimateHas donemob or pairprogrammingHas seen ateam gofrom chaosto highperformanceHas workedin an orgwhere Agilewas “only forengineering"Has witnessedan epic debateover storypoints vs. timeestimatesHasworked ona KanbanteamHas had toexplain that“Scrum” and“Agile” are notthe same thingHas had astakeholderdemand adeadlinewithout contextHas tried anew Agileframework(SAFe,LeSS, etc.)Has been ina standupthat lastedover 30minutesHas seen anAgiletransformationstruggleHas arguedabout whatDefinition ofReady or Doneshould includeHas workedwith a team thatonly did Agileceremonies butdidn’t embraceAgile valuesHas coacheda teamthrough theirfirstretrospectiveHas been partof anexperiment thattotally failed—but learned alot!Has seen aProduct Owneract as a projectmanager insteadof a value-drivenleaderHas run aretro thatwent offthe railsHas heard“We’re Agile, sowe don’t needdocumentation”Has beenpart of anun-conferenceHas workedon a teamwith nodedicatedScrum MasterHas hadto defendWIP limitsHas been ona team thatabandonedstandupsHasparticipatedin a LeanCoffeesessionHas taughtsomeoneabout AgileHas beentold Agiledoesn’t workin “ourspace/team”Has seen ateam self-organize in apowerful way

Agile CoP 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
25
26
27
28
29
30
31
32
33
34
  1. Has experienced “water-Scrum-fall”
  2. Has witnessed a team commit to way more work than they could realistically complete in a sprint
  3. Loves or hates Jira passionately
  4. Has been on a team that monitored cycle time and actively tried to decrease it
  5. Has worked on a fully collocated Agile team
  6. Has done a fun retrospective format
  7. Has worked with a truly amazing Product Owner
  8. Has seen a team struggle with too many priorities at once
  9. Has been part of a team that changed how they estimate
  10. Has done mob or pair programming
  11. Has seen a team go from chaos to high performance
  12. Has worked in an org where Agile was “only for engineering"
  13. Has witnessed an epic debate over story points vs. time estimates
  14. Has worked on a Kanban team
  15. Has had to explain that “Scrum” and “Agile” are not the same thing
  16. Has had a stakeholder demand a deadline without context
  17. Has tried a new Agile framework (SAFe, LeSS, etc.)
  18. Has been in a standup that lasted over 30 minutes
  19. Has seen an Agile transformation struggle
  20. Has argued about what Definition of Ready or Done should include
  21. Has worked with a team that only did Agile ceremonies but didn’t embrace Agile values
  22. Has coached a team through their first retrospective
  23. Has been part of an experiment that totally failed—but learned a lot!
  24. Has seen a Product Owner act as a project manager instead of a value-driven leader
  25. Has run a retro that went off the rails
  26. Has heard “We’re Agile, so we don’t need documentation”
  27. Has been part of an un-conference
  28. Has worked on a team with no dedicated Scrum Master
  29. Has had to defend WIP limits
  30. Has been on a team that abandoned standups
  31. Has participated in a Lean Coffee session
  32. Has taught someone about Agile
  33. Has been told Agile doesn’t work in “our space/team”
  34. Has seen a team self-organize in a powerful way