UseKanbanswimlanesThe team isautonomousRetros areconsistentlyheldStill havewaterfallartifacts likerqt docs orproject plansRetrospectiveaction itemsare regularlycompletedTeammembersare on morethan oneteamStand upgoeslonger than15 minutesOnedefinedProductOwnerKanban WIPlimits are a"suggestion"Managersregularlydole outtasksPerformreleaseplanningOrderedbacklogHave aDoD that'sfollowedconsistentlyHave adefinedDoRThere'snever anyconflict onthe teamStakeholdersand teamattend SprintReviewThe ScrumMaster ormanagertracks theteam's work Everyone onthe team is100%committed tothe teamSMs andmanagersact asservantleadersAll artifactslike thebacklog arefullytransparentRefinementis more than10% of theteam's timeTeammembersfeel safeTeam ismore than9 peopleUse agilemetrics likevelocity, leadand cycletimesUseKanbanswimlanesThe team isautonomousRetros areconsistentlyheldStill havewaterfallartifacts likerqt docs orproject plansRetrospectiveaction itemsare regularlycompletedTeammembersare on morethan oneteamStand upgoeslonger than15 minutesOnedefinedProductOwnerKanban WIPlimits are a"suggestion"Managersregularlydole outtasksPerformreleaseplanningOrderedbacklogHave aDoD that'sfollowedconsistentlyHave adefinedDoRThere'snever anyconflict onthe teamStakeholdersand teamattend SprintReviewThe ScrumMaster ormanagertracks theteam's work Everyone onthe team is100%committed tothe teamSMs andmanagersact asservantleadersAll artifactslike thebacklog arefullytransparentRefinementis more than10% of theteam's timeTeammembersfeel safeTeam ismore than9 peopleUse agilemetrics likevelocity, leadand cycletimes

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