There'snever anyconflict onthe teamStakeholdersand teamattend SprintReviewHave adefinedDoRAll artifactslike thebacklog arefullytransparentThe ScrumMaster ormanagertracks theteam's work Refinementis more than10% of theteam's timeTeam ismore than9 peopleOrderedbacklogSMs andmanagersact asservantleadersOnedefinedProductOwnerUseKanbanswimlanesManagersregularlydole outtasksStill havewaterfallartifacts likerqt docs orproject plansEveryone onthe team is100%committed tothe teamUse agilemetrics likevelocity, leadand cycletimesTeammembersfeel safeRetrospectiveaction itemsare regularlycompletedPerformreleaseplanningKanban WIPlimits are a"suggestion"Teammembersare on morethan oneteamStand upgoeslonger than15 minutesRetros areconsistentlyheldThe team isautonomousHave aDoD that'sfollowedconsistentlyThere'snever anyconflict onthe teamStakeholdersand teamattend SprintReviewHave adefinedDoRAll artifactslike thebacklog arefullytransparentThe ScrumMaster ormanagertracks theteam's work Refinementis more than10% of theteam's timeTeam ismore than9 peopleOrderedbacklogSMs andmanagersact asservantleadersOnedefinedProductOwnerUseKanbanswimlanesManagersregularlydole outtasksStill havewaterfallartifacts likerqt docs orproject plansEveryone onthe team is100%committed tothe teamUse agilemetrics likevelocity, leadand cycletimesTeammembersfeel safeRetrospectiveaction itemsare regularlycompletedPerformreleaseplanningKanban WIPlimits are a"suggestion"Teammembersare on morethan oneteamStand upgoeslonger than15 minutesRetros areconsistentlyheldThe team isautonomousHave aDoD that'sfollowedconsistently

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