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

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