The ScrumMaster ormanagertracks theteam's work Retros areconsistentlyheldEveryone onthe team is100%committed tothe teamStill havewaterfallartifacts likerqt docs orproject plansThe team isautonomousSMs andmanagersact asservantleadersHave adefinedDoRUse agilemetrics likevelocity, leadand cycletimesUseKanbanswimlanesStand upgoeslonger than15 minutesOrderedbacklogTeam ismore than9 peopleOnedefinedProductOwnerHave aDoD that'sfollowedconsistentlyRetrospectiveaction itemsare regularlycompletedRefinementis more than10% of theteam's timePerformreleaseplanningThere'snever anyconflict onthe teamStakeholdersand teamattend SprintReviewTeammembersare on morethan oneteamManagersregularlydole outtasksAll artifactslike thebacklog arefullytransparentTeammembersfeel safeKanban WIPlimits are a"suggestion"The ScrumMaster ormanagertracks theteam's work Retros areconsistentlyheldEveryone onthe team is100%committed tothe teamStill havewaterfallartifacts likerqt docs orproject plansThe team isautonomousSMs andmanagersact asservantleadersHave adefinedDoRUse agilemetrics likevelocity, leadand cycletimesUseKanbanswimlanesStand upgoeslonger than15 minutesOrderedbacklogTeam ismore than9 peopleOnedefinedProductOwnerHave aDoD that'sfollowedconsistentlyRetrospectiveaction itemsare regularlycompletedRefinementis more than10% of theteam's timePerformreleaseplanningThere'snever anyconflict onthe teamStakeholdersand teamattend SprintReviewTeammembersare on morethan oneteamManagersregularlydole outtasksAll artifactslike thebacklog arefullytransparentTeammembersfeel safeKanban 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. The Scrum Master or manager tracks the team's work
  2. Retros are consistently held
  3. Everyone on the team is 100% committed to the team
  4. Still have waterfall artifacts like rqt docs or project plans
  5. The team is autonomous
  6. SMs and managers act as servant leaders
  7. Have a defined DoR
  8. Use agile metrics like velocity, lead and cycle times
  9. Use Kanban swimlanes
  10. Stand up goes longer than 15 minutes
  11. Ordered backlog
  12. Team is more than 9 people
  13. One defined Product Owner
  14. Have a DoD that's followed consistently
  15. Retrospective action items are regularly completed
  16. Refinement is more than 10% of the team's time
  17. Perform release planning
  18. There's never any conflict on the team
  19. Stakeholders and team attend Sprint Review
  20. Team members are on more than one team
  21. Managers regularly dole out tasks
  22. All artifacts like the backlog are fully transparent
  23. Team members feel safe
  24. Kanban WIP limits are a "suggestion"