DocumentationMultitaskingacrossticketsLettingwork pileup in“Review”Ticket tooBig - breakdown intosmallest bitof valueStop/startwork withall thefunctionsNewTeamTerri isthe bestPO 🥇DontdiscussPriority instandupScopecreepLearnedalotWe saweachotherIRLTests arepainful butnecessaryWeeklyprioritizationsessions forPOsGetengineeringlead to checktickets beforethey are addedin the queueDadjokesContextswitchingWesupportedeach otherreally wellOurdeploymentcaused a(minor) bugStartedwithout aclearsolution inmindTeamworkPrioritizingknowledgesharingUsing Slackthreads forclarity/UpdatesHavecamerasonUpdatingticketsregularlyPairProgramingUsingasyncthreadswellAlways testfull flow ofwork beforeasking forreviewSubtaskswere addedmid-waywhen we gotstuckClearAcceptancecriteriaDocumentationMultitaskingacrossticketsLettingwork pileup in“Review”Ticket tooBig - breakdown intosmallest bitof valueStop/startwork withall thefunctionsNewTeamTerri isthe bestPO 🥇DontdiscussPriority instandupScopecreepLearnedalotWe saweachotherIRLTests arepainful butnecessaryWeeklyprioritizationsessions forPOsGetengineeringlead to checktickets beforethey are addedin the queueDadjokesContextswitchingWesupportedeach otherreally wellOurdeploymentcaused a(minor) bugStartedwithout aclearsolution inmindTeamworkPrioritizingknowledgesharingUsing Slackthreads forclarity/UpdatesHavecamerasonUpdatingticketsregularlyPairProgramingUsingasyncthreadswellAlways testfull flow ofwork beforeasking forreviewSubtaskswere addedmid-waywhen we gotstuckClearAcceptancecriteria

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