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

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