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

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