DadjokesWeeklyprioritizationsessions forPOsTeamworkDocumentationScopecreepClearAcceptancecriteriaUsing Slackthreads forclarity/UpdatesUsingasyncthreadswellWesupportedeach otherreally wellTicket tooBig - breakdown intosmallest bitof valueLearnedalotNewTeamStop/startwork withall thefunctionsPrioritizingknowledgesharingWe saweachotherIRLAlways testfull flow ofwork beforeasking forreviewContextswitchingUpdatingticketsregularlyTests arepainful butnecessaryStartedwithout aclearsolution inmindGetengineeringlead to checktickets beforethey are addedin the queuePairProgramingSubtaskswere addedmid-waywhen we gotstuckMultitaskingacrossticketsDontdiscussPriority instandupLettingwork pileup in“Review”Terri isthe bestPO 🥇HavecamerasonOurdeploymentcaused a(minor) bugDadjokesWeeklyprioritizationsessions forPOsTeamworkDocumentationScopecreepClearAcceptancecriteriaUsing Slackthreads forclarity/UpdatesUsingasyncthreadswellWesupportedeach otherreally wellTicket tooBig - breakdown intosmallest bitof valueLearnedalotNewTeamStop/startwork withall thefunctionsPrioritizingknowledgesharingWe saweachotherIRLAlways testfull flow ofwork beforeasking forreviewContextswitchingUpdatingticketsregularlyTests arepainful butnecessaryStartedwithout aclearsolution inmindGetengineeringlead to checktickets beforethey are addedin the queuePairProgramingSubtaskswere addedmid-waywhen we gotstuckMultitaskingacrossticketsDontdiscussPriority instandupLettingwork pileup in“Review”Terri isthe bestPO 🥇HavecamerasonOurdeploymentcaused a(minor) bug

Atlas Retro 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
25
26
27
28
29
  1. Dad jokes
  2. Weekly prioritization sessions for POs
  3. Team work
  4. Documentation
  5. Scope creep
  6. Clear Acceptance criteria
  7. Using Slack threads for clarity/Updates
  8. Using async threads well
  9. We supported each other really well
  10. Ticket too Big - break down into smallest bit of value
  11. Learned alot
  12. New Team
  13. Stop/start work with all the functions
  14. Prioritizing knowledge sharing
  15. We saw eachother IRL
  16. Always test full flow of work before asking for review
  17. Context switching
  18. Updating tickets regularly
  19. Tests are painful but necessary
  20. Started without a clear solution in mind
  21. Get engineering lead to check tickets before they are added in the queue
  22. Pair Programing
  23. Subtasks were added mid-way when we got stuck
  24. Multitasking across tickets
  25. Dont discuss Priority in standup
  26. Letting work pile up in “Review”
  27. Terri is the best PO 🥇
  28. Have cameras on
  29. Our deployment caused a (minor) bug