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

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