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

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