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

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