Still havewaterfallartifacts likerqt docs orproject plansTeam ismore than9 peopleTeammembersare on morethan oneteamHave adefinedDoRRetrospectiveaction itemsare regularlycompletedOrderedbacklogThe ScrumMaster ormanagertracks theteam's work Managersregularlydole outtasksTeammembersfeel safeRetros areconsistentlyheldUse agilemetrics likevelocity, leadand cycletimesUseKanbanswimlanesPerformreleaseplanningOnedefinedProductOwnerHave aDoD that'sfollowedconsistentlyAll artifactslike thebacklog arefullytransparentStakeholdersand teamattend SprintReviewSMs andmanagersact asservantleadersThe team isautonomousStand upgoeslonger than15 minutesEveryone onthe team is100%committed tothe teamThere'snever anyconflict onthe teamRefinementis more than10% of theteam's timeKanban WIPlimits are a"suggestion"Still havewaterfallartifacts likerqt docs orproject plansTeam ismore than9 peopleTeammembersare on morethan oneteamHave adefinedDoRRetrospectiveaction itemsare regularlycompletedOrderedbacklogThe ScrumMaster ormanagertracks theteam's work Managersregularlydole outtasksTeammembersfeel safeRetros areconsistentlyheldUse agilemetrics likevelocity, leadand cycletimesUseKanbanswimlanesPerformreleaseplanningOnedefinedProductOwnerHave aDoD that'sfollowedconsistentlyAll artifactslike thebacklog arefullytransparentStakeholdersand teamattend SprintReviewSMs andmanagersact asservantleadersThe team isautonomousStand upgoeslonger than15 minutesEveryone onthe team is100%committed tothe teamThere'snever anyconflict onthe teamRefinementis more than10% of theteam's timeKanban WIPlimits are a"suggestion"

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