Still havewaterfallartifacts likerqt docs orproject plansTeam ismore than9 peopleTeammembersare on morethan oneteamThere'snever anyconflict onthe teamOrderedbacklogEveryone onthe team is100%committed tothe teamUse agilemetrics likevelocity, leadand cycletimesTeammembersfeel safeThe ScrumMaster ormanagertracks theteam's work PerformreleaseplanningOnedefinedProductOwnerThe team isautonomousManagersregularlydole outtasksRefinementis more than10% of theteam's timeRetros areconsistentlyheldKanban WIPlimits are a"suggestion"Stand upgoeslonger than15 minutesUseKanbanswimlanesHave aDoD that'sfollowedconsistentlyRetrospectiveaction itemsare regularlycompletedSMs andmanagersact asservantleadersHave adefinedDoRAll artifactslike thebacklog arefullytransparentStakeholdersand teamattend SprintReviewStill havewaterfallartifacts likerqt docs orproject plansTeam ismore than9 peopleTeammembersare on morethan oneteamThere'snever anyconflict onthe teamOrderedbacklogEveryone onthe team is100%committed tothe teamUse agilemetrics likevelocity, leadand cycletimesTeammembersfeel safeThe ScrumMaster ormanagertracks theteam's work PerformreleaseplanningOnedefinedProductOwnerThe team isautonomousManagersregularlydole outtasksRefinementis more than10% of theteam's timeRetros areconsistentlyheldKanban WIPlimits are a"suggestion"Stand upgoeslonger than15 minutesUseKanbanswimlanesHave aDoD that'sfollowedconsistentlyRetrospectiveaction itemsare regularlycompletedSMs andmanagersact asservantleadersHave adefinedDoRAll artifactslike thebacklog arefullytransparentStakeholdersand teamattend SprintReview

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