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

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