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

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