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

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