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

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