Team ismore than9 peopleHave adefinedDoRHave aDoD that'sfollowedconsistentlyManagersregularlydole outtasksPerformreleaseplanningStill havewaterfallartifacts likerqt docs orproject plansSMs andmanagersact asservantleadersRetros areconsistentlyheldThe ScrumMaster ormanagertracks theteam's work OnedefinedProductOwnerRefinementis more than10% of theteam's timeEveryone onthe team is100%committed tothe teamUse agilemetrics likevelocity, leadand cycletimesThe team isautonomousRetrospectiveaction itemsare regularlycompletedKanban WIPlimits are a"suggestion"There'snever anyconflict onthe teamAll artifactslike thebacklog arefullytransparentTeammembersfeel safeStand upgoeslonger than15 minutesStakeholdersand teamattend SprintReviewOrderedbacklogUseKanbanswimlanesTeammembersare on morethan oneteamTeam ismore than9 peopleHave adefinedDoRHave aDoD that'sfollowedconsistentlyManagersregularlydole outtasksPerformreleaseplanningStill havewaterfallartifacts likerqt docs orproject plansSMs andmanagersact asservantleadersRetros areconsistentlyheldThe ScrumMaster ormanagertracks theteam's work OnedefinedProductOwnerRefinementis more than10% of theteam's timeEveryone onthe team is100%committed tothe teamUse agilemetrics likevelocity, leadand cycletimesThe team isautonomousRetrospectiveaction itemsare regularlycompletedKanban WIPlimits are a"suggestion"There'snever anyconflict onthe teamAll artifactslike thebacklog arefullytransparentTeammembersfeel safeStand upgoeslonger than15 minutesStakeholdersand teamattend SprintReviewOrderedbacklogUseKanbanswimlanesTeammembersare on morethan oneteam

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