There'snever anyconflict onthe teamUse agilemetrics likevelocity, leadand cycletimesOnedefinedProductOwnerThe ScrumMaster ormanagertracks theteam's work Teammembersfeel safeRetrospectiveaction itemsare regularlycompletedTeam ismore than9 peoplePerformreleaseplanningKanban WIPlimits are a"suggestion"Refinementis more than10% of theteam's timeTeammembersare on morethan oneteamHave adefinedDoRStand upgoeslonger than15 minutesStill havewaterfallartifacts likerqt docs orproject plansHave aDoD that'sfollowedconsistentlyManagersregularlydole outtasksStakeholdersand teamattend SprintReviewOrderedbacklogUseKanbanswimlanesRetros areconsistentlyheldThe team isautonomousSMs andmanagersact asservantleadersEveryone onthe team is100%committed tothe teamAll artifactslike thebacklog arefullytransparentThere'snever anyconflict onthe teamUse agilemetrics likevelocity, leadand cycletimesOnedefinedProductOwnerThe ScrumMaster ormanagertracks theteam's work Teammembersfeel safeRetrospectiveaction itemsare regularlycompletedTeam ismore than9 peoplePerformreleaseplanningKanban WIPlimits are a"suggestion"Refinementis more than10% of theteam's timeTeammembersare on morethan oneteamHave adefinedDoRStand upgoeslonger than15 minutesStill havewaterfallartifacts likerqt docs orproject plansHave aDoD that'sfollowedconsistentlyManagersregularlydole outtasksStakeholdersand teamattend SprintReviewOrderedbacklogUseKanbanswimlanesRetros areconsistentlyheldThe team isautonomousSMs andmanagersact asservantleadersEveryone onthe team is100%committed tothe teamAll artifactslike thebacklog arefullytransparent

Blue Agile 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
  1. There's never any conflict on the team
  2. Use agile metrics like velocity, lead and cycle times
  3. One defined Product Owner
  4. The Scrum Master or manager tracks the team's work
  5. Team members feel safe
  6. Retrospective action items are regularly completed
  7. Team is more than 9 people
  8. Perform release planning
  9. Kanban WIP limits are a "suggestion"
  10. Refinement is more than 10% of the team's time
  11. Team members are on more than one team
  12. Have a defined DoR
  13. Stand up goes longer than 15 minutes
  14. Still have waterfall artifacts like rqt docs or project plans
  15. Have a DoD that's followed consistently
  16. Managers regularly dole out tasks
  17. Stakeholders and team attend Sprint Review
  18. Ordered backlog
  19. Use Kanban swimlanes
  20. Retros are consistently held
  21. The team is autonomous
  22. SMs and managers act as servant leaders
  23. Everyone on the team is 100% committed to the team
  24. All artifacts like the backlog are fully transparent