Retrospectiveaction itemsare regularlycompletedStill havewaterfallartifacts likerqt docs orproject plansUse agilemetrics likevelocity, leadand cycletimesTeam ismore than9 peopleAll artifactslike thebacklog arefullytransparentThe ScrumMaster ormanagertracks theteam's work Have aDoD that'sfollowedconsistentlyThere'snever anyconflict onthe teamKanban WIPlimits are a"suggestion"UseKanbanswimlanesRefinementis more than10% of theteam's timeHave adefinedDoRTeammembersfeel safeSMs andmanagersact asservantleadersStand upgoeslonger than15 minutesOrderedbacklogOnedefinedProductOwnerPerformreleaseplanningTeammembersare on morethan oneteamStakeholdersand teamattend SprintReviewThe team isautonomousEveryone onthe team is100%committed tothe teamManagersregularlydole outtasksRetros areconsistentlyheldRetrospectiveaction itemsare regularlycompletedStill havewaterfallartifacts likerqt docs orproject plansUse agilemetrics likevelocity, leadand cycletimesTeam ismore than9 peopleAll artifactslike thebacklog arefullytransparentThe ScrumMaster ormanagertracks theteam's work Have aDoD that'sfollowedconsistentlyThere'snever anyconflict onthe teamKanban WIPlimits are a"suggestion"UseKanbanswimlanesRefinementis more than10% of theteam's timeHave adefinedDoRTeammembersfeel safeSMs andmanagersact asservantleadersStand upgoeslonger than15 minutesOrderedbacklogOnedefinedProductOwnerPerformreleaseplanningTeammembersare on morethan oneteamStakeholdersand teamattend SprintReviewThe team isautonomousEveryone onthe team is100%committed tothe teamManagersregularlydole outtasksRetros areconsistentlyheld

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