Retrospectiveaction itemsare regularlycompletedUseKanbanswimlanesThere'snever anyconflict onthe teamKanban WIPlimits are a"suggestion"Managersregularlydole outtasksHave adefinedDoRStill havewaterfallartifacts likerqt docs orproject plansRefinementis more than10% of theteam's timeTeam ismore than9 peopleEveryone onthe team is100%committed tothe teamTeammembersfeel safeThe team isautonomousOrderedbacklogRetros areconsistentlyheldThe ScrumMaster ormanagertracks theteam's work Use agilemetrics likevelocity, leadand cycletimesStand upgoeslonger than15 minutesPerformreleaseplanningOnedefinedProductOwnerAll artifactslike thebacklog arefullytransparentSMs andmanagersact asservantleadersStakeholdersand teamattend SprintReviewHave aDoD that'sfollowedconsistentlyTeammembersare on morethan oneteamRetrospectiveaction itemsare regularlycompletedUseKanbanswimlanesThere'snever anyconflict onthe teamKanban WIPlimits are a"suggestion"Managersregularlydole outtasksHave adefinedDoRStill havewaterfallartifacts likerqt docs orproject plansRefinementis more than10% of theteam's timeTeam ismore than9 peopleEveryone onthe team is100%committed tothe teamTeammembersfeel safeThe team isautonomousOrderedbacklogRetros areconsistentlyheldThe ScrumMaster ormanagertracks theteam's work Use agilemetrics likevelocity, leadand cycletimesStand upgoeslonger than15 minutesPerformreleaseplanningOnedefinedProductOwnerAll artifactslike thebacklog arefullytransparentSMs andmanagersact asservantleadersStakeholdersand teamattend SprintReviewHave aDoD that'sfollowedconsistentlyTeammembersare on morethan oneteam

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