Has done afunretrospectiveformatHas beenpart of anun-conferenceHas run aretro thatwent offthe railsHas seen ateam gofrom chaosto highperformanceHas hadto defendWIP limitsHas been ona team thatabandonedstandupsHas been ina standupthat lastedover 30minutesHas workedwith a team thatonly did Agileceremonies butdidn’t embraceAgile valuesHas donemob or pairprogrammingHas witnessedan epic debateover storypoints vs. timeestimatesHas beenpart of ateam thatchanged howthey estimateHas workedon a fullycollocatedAgile teamLoves orhates JirapassionatelyHas workedin an orgwhere Agilewas “only forengineering"Has seen ateam strugglewith too manypriorities atonceHas workedwith a trulyamazingProductOwnerHas had astakeholderdemand adeadlinewithout contextHas workedon a teamwith nodedicatedScrum MasterHas taughtsomeoneabout AgileHas been partof anexperiment thattotally failed—but learned alot!Hasworked ona KanbanteamHas seen anAgiletransformationstruggleHas arguedabout whatDefinition ofReady or Doneshould includeHas witnessed ateam commit toway more workthan they couldrealisticallycomplete in asprintHas heard“We’re Agile, sowe don’t needdocumentation”Has coacheda teamthrough theirfirstretrospectiveHas had toexplain that“Scrum” and“Agile” are notthe same thingHas seen ateam self-organize in apowerful wayHasexperienced“water-Scrum-fall”Has seen aProduct Owneract as a projectmanager insteadof a value-drivenleaderHas been on ateam thatmonitored cycletime andactively tried todecrease itHasparticipatedin a LeanCoffeesessionHas tried anew Agileframework(SAFe,LeSS, etc.)Has beentold Agiledoesn’t workin “ourspace/team”Has done afunretrospectiveformatHas beenpart of anun-conferenceHas run aretro thatwent offthe railsHas seen ateam gofrom chaosto highperformanceHas hadto defendWIP limitsHas been ona team thatabandonedstandupsHas been ina standupthat lastedover 30minutesHas workedwith a team thatonly did Agileceremonies butdidn’t embraceAgile valuesHas donemob or pairprogrammingHas witnessedan epic debateover storypoints vs. timeestimatesHas beenpart of ateam thatchanged howthey estimateHas workedon a fullycollocatedAgile teamLoves orhates JirapassionatelyHas workedin an orgwhere Agilewas “only forengineering"Has seen ateam strugglewith too manypriorities atonceHas workedwith a trulyamazingProductOwnerHas had astakeholderdemand adeadlinewithout contextHas workedon a teamwith nodedicatedScrum MasterHas taughtsomeoneabout AgileHas been partof anexperiment thattotally failed—but learned alot!Hasworked ona KanbanteamHas seen anAgiletransformationstruggleHas arguedabout whatDefinition ofReady or Doneshould includeHas witnessed ateam commit toway more workthan they couldrealisticallycomplete in asprintHas heard“We’re Agile, sowe don’t needdocumentation”Has coacheda teamthrough theirfirstretrospectiveHas had toexplain that“Scrum” and“Agile” are notthe same thingHas seen ateam self-organize in apowerful wayHasexperienced“water-Scrum-fall”Has seen aProduct Owneract as a projectmanager insteadof a value-drivenleaderHas been on ateam thatmonitored cycletime andactively tried todecrease itHasparticipatedin a LeanCoffeesessionHas tried anew Agileframework(SAFe,LeSS, etc.)Has 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. Has done a fun retrospective format
  2. Has been part of an un-conference
  3. Has run a retro that went off the rails
  4. Has seen a team go from chaos to high performance
  5. Has had to defend WIP limits
  6. Has been on a team that abandoned standups
  7. Has been in a standup that lasted over 30 minutes
  8. Has worked with a team that only did Agile ceremonies but didn’t embrace Agile values
  9. Has done mob or pair programming
  10. Has witnessed an epic debate over story points vs. time estimates
  11. Has been part of a team that changed how they estimate
  12. Has worked on a fully collocated Agile team
  13. Loves or hates Jira passionately
  14. Has worked in an org where Agile was “only for engineering"
  15. Has seen a team struggle with too many priorities at once
  16. Has worked with a truly amazing Product Owner
  17. Has had a stakeholder demand a deadline without context
  18. Has worked on a team with no dedicated Scrum Master
  19. Has taught someone about Agile
  20. Has been part of an experiment that totally failed—but learned a lot!
  21. Has worked on a Kanban team
  22. Has seen an Agile transformation struggle
  23. Has argued about what Definition of Ready or Done should include
  24. Has witnessed a team commit to way more work than they could realistically complete in a sprint
  25. Has heard “We’re Agile, so we don’t need documentation”
  26. Has coached a team through their first retrospective
  27. Has had to explain that “Scrum” and “Agile” are not the same thing
  28. Has seen a team self-organize in a powerful way
  29. Has experienced “water-Scrum-fall”
  30. Has seen a Product Owner act as a project manager instead of a value-driven leader
  31. Has been on a team that monitored cycle time and actively tried to decrease it
  32. Has participated in a Lean Coffee session
  33. Has tried a new Agile framework (SAFe, LeSS, etc.)
  34. Has been told Agile doesn’t work in “our space/team”