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

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