ProductBacklogStakeholderSwimlaneSprintContinuousDeliveryTimeboxcrossfunctionalRelativeEstimationSprintBacklogPairProgrammingArtifactProductVisionTechnicalDebtStoryPointsBug/Story/TaskCourageMinimumViableProductScrumFrameworkSprintboard 5swim laneCoachZombieScrumWhat is aSustainablePace?Self-OrganizingTransparentSpikeManagerDailyScrumBusinessValueSprintCodeQualityTeamMemberReleasePlanningScrumBoardScrumEventPotentiallyReleasableProductIncrementWorkingsoftwareScalingScrumFibonacciSequenceFacilitatorPrototypingRespectwhy Retroimportant?StorySlicingSwarmingUserStoryOne-PieceFlowScrumMasterContinuousIntegrationuserstorytemplateDevelopmentTeamVelocityCross-Functionalcan weskipceremoniesSprintReviewServantLeadershipBurndownProductOwnerWork-In-ProgressDeveloperInspect&AdaptAcceptanceCriteriaEpicEmpiricalProcessOpennessStakeholderManagementMVPINVESTScopeCreepZombieScrumAutomatedTestingVelocityCommitmentFocusChallengeStorySlicingCommitmentthreepillars ofscrumPlanningPokerProductBacklogStakeholderSwimlaneSprintContinuousDeliveryTimeboxcrossfunctionalRelativeEstimationSprintBacklogPairProgrammingArtifactProductVisionTechnicalDebtStoryPointsBug/Story/TaskCourageMinimumViableProductScrumFrameworkSprintboard 5swim laneCoachZombieScrumWhat is aSustainablePace?Self-OrganizingTransparentSpikeManagerDailyScrumBusinessValueSprintCodeQualityTeamMemberReleasePlanningScrumBoardScrumEventPotentiallyReleasableProductIncrementWorkingsoftwareScalingScrumFibonacciSequenceFacilitatorPrototypingRespectwhy Retroimportant?StorySlicingSwarmingUserStoryOne-PieceFlowScrumMasterContinuousIntegrationuserstorytemplateDevelopmentTeamVelocityCross-Functionalcan weskipceremoniesSprintReviewServantLeadershipBurndownProductOwnerWork-In-ProgressDeveloperInspect&AdaptAcceptanceCriteriaEpicEmpiricalProcessOpennessStakeholderManagementMVPINVESTScopeCreepZombieScrumAutomatedTestingVelocityCommitmentFocusChallengeStorySlicingCommitmentthreepillars ofscrumPlanningPoker

AGILE BINGO for Team - 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
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
  1. Product Backlog
  2. Stakeholder
  3. Swimlane
  4. Sprint
  5. Continuous Delivery
  6. Timebox
  7. cross functional
  8. Relative Estimation
  9. Sprint Backlog
  10. Pair Programming
  12. Artifact
  13. Product Vision
  14. Technical Debt
  15. Story Points
  16. Bug/Story/Task
  17. Courage
  18. Minimum Viable Product
  19. Scrum Framework
  20. Sprint board 5 swim lane
  21. Coach
  22. Zombie Scrum
  23. What is a Sustainable Pace?
  24. Self-Organizing
  25. Transparent
  26. Spike
  27. Manager
  28. Daily Scrum
  29. Business Value
  30. Sprint
  31. Code Quality
  32. Team Member
  33. Release Planning
  34. Scrum Board
  35. Scrum Event
  36. Potentially Releasable Product Increment
  37. Working software
  38. Scaling Scrum
  39. Fibonacci Sequence
  40. Facilitator
  41. Prototyping
  42. Respect
  43. why Retro important?
  44. Story Slicing
  45. Swarming
  46. User Story
  47. One-Piece Flow
  48. Scrum Master
  49. Continuous Integration
  50. user story template
  51. Development Team
  52. Velocity
  53. Cross-Functional
  54. can we skip ceremonies
  55. Sprint Review
  56. Servant Leadership
  57. Burndown
  58. Product Owner
  60. Work-In-Progress
  61. Developer
  62. Inspect & Adapt
  63. Acceptance Criteria
  64. Epic
  65. Empirical Process
  66. Openness
  67. Stakeholder Management
  68. MVP
  69. INVEST
  70. Scope Creep
  71. Zombie Scrum
  72. Automated Testing
  73. Velocity
  74. Commitment
  75. Focus
  76. Challenge
  77. Story Slicing
  78. Commitment
  79. three pillars of scrum
  80. Planning Poker