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

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