Retros areconsistentlyheldOnedefinedProductOwnerTeam ismore than9 peopleStill havewaterfallartifacts likerqt docs orproject plansStand upgoeslonger than15 minutesEveryone onthe team is100%committed tothe teamManagersregularlydole outtasksRefinementis more than10% of theteam's timeStakeholdersand teamattend SprintReviewThe team isautonomousHave aDoD that'sfollowedconsistentlyHave adefinedDoROrderedbacklogUse agilemetrics likevelocity, leadand cycletimesPerformreleaseplanningRetrospectiveaction itemsare regularlycompletedTeammembersare on morethan oneteamTeammembersfeel safeUseKanbanswimlanesSMs andmanagersact asservantleadersKanban WIPlimits are a"suggestion"The ScrumMaster ormanagertracks theteam's work All artifactslike thebacklog arefullytransparentThere'snever anyconflict onthe teamRetros areconsistentlyheldOnedefinedProductOwnerTeam ismore than9 peopleStill havewaterfallartifacts likerqt docs orproject plansStand upgoeslonger than15 minutesEveryone onthe team is100%committed tothe teamManagersregularlydole outtasksRefinementis more than10% of theteam's timeStakeholdersand teamattend SprintReviewThe team isautonomousHave aDoD that'sfollowedconsistentlyHave adefinedDoROrderedbacklogUse agilemetrics likevelocity, leadand cycletimesPerformreleaseplanningRetrospectiveaction itemsare regularlycompletedTeammembersare on morethan oneteamTeammembersfeel safeUseKanbanswimlanesSMs andmanagersact asservantleadersKanban WIPlimits are a"suggestion"The ScrumMaster ormanagertracks theteam's work All artifactslike thebacklog arefullytransparentThere'snever anyconflict onthe team

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