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

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