LETTHEMFIGHTQAFree!QuestionsChallengeMeeting(s)GitHubDeveloper(s)Someone doesn'tbother to pass onknowledge so anewer teammember can dotheir jobBugJira"GoodMorning"SomeoneblamesSFDevOpsCommunicationProcessStickies"I needsomeonetoexplain..."SlackDevelopmentCommentsDEV teams turnon each otherfor a change.SF DevOpseats popcorn.Colecomments inTeamsinstead ofspeakingUpdateRetro isderailed forat least fiveminutesSomeonecomplainsbut doesn'toffer asolutionLETTHEMFIGHTQAFree!QuestionsChallengeMeeting(s)GitHubDeveloper(s)Someone doesn'tbother to pass onknowledge so anewer teammember can dotheir jobBugJira"GoodMorning"SomeoneblamesSFDevOpsCommunicationProcessStickies"I needsomeonetoexplain..."SlackDevelopmentCommentsDEV teams turnon each otherfor a change.SF DevOpseats popcorn.Colecomments inTeamsinstead ofspeakingUpdateRetro isderailed forat least fiveminutesSomeonecomplainsbut doesn'toffer asolution

MBMS ART Retro - 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
25
  1. LET THEM FIGHT
  2. QA
  3. Free!
  4. Questions
  5. Challenge
  6. Meeting(s)
  7. GitHub
  8. Developer(s)
  9. Someone doesn't bother to pass on knowledge so a newer team member can do their job
  10. Bug
  11. Jira
  12. "Good Morning"
  13. Someone blames SF DevOps
  14. Communication
  15. Process
  16. Stickies
  17. "I need someone to explain..."
  18. Slack
  19. Development
  20. Comments
  21. DEV teams turn on each other for a change. SF DevOps eats popcorn.
  22. Cole comments in Teams instead of speaking
  23. Update
  24. Retro is derailed for at least five minutes
  25. Someone complains but doesn't offer a solution