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

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