MultitaskingacrossticketsLearnedalotGetengineeringlead to checktickets beforethey are addedin the queueContextswitchingUpdatingticketsregularlyUsingasyncthreadswellWe saweachotherIRLDadjokesSubtaskswere addedmid-waywhen we gotstuckTerri isthe bestPO 🥇Weeklyprioritizationsessions forPOsDontdiscussPriority instandupWesupportedeach otherreally wellOurdeploymentcaused a(minor) bugTicket tooBig - breakdown intosmallest bitof valueStartedwithout aclearsolution inmindAlways testfull flow ofwork beforeasking forreviewPairProgramingLettingwork pileup in“Review”PrioritizingknowledgesharingDocumentationStop/startwork withall thefunctionsUsing Slackthreads forclarity/UpdatesNewTeamClearAcceptancecriteriaTeamworkHavecamerasonScopecreepTests arepainful butnecessaryMultitaskingacrossticketsLearnedalotGetengineeringlead to checktickets beforethey are addedin the queueContextswitchingUpdatingticketsregularlyUsingasyncthreadswellWe saweachotherIRLDadjokesSubtaskswere addedmid-waywhen we gotstuckTerri isthe bestPO 🥇Weeklyprioritizationsessions forPOsDontdiscussPriority instandupWesupportedeach otherreally wellOurdeploymentcaused a(minor) bugTicket tooBig - breakdown intosmallest bitof valueStartedwithout aclearsolution inmindAlways testfull flow ofwork beforeasking forreviewPairProgramingLettingwork pileup in“Review”PrioritizingknowledgesharingDocumentationStop/startwork withall thefunctionsUsing Slackthreads forclarity/UpdatesNewTeamClearAcceptancecriteriaTeamworkHavecamerasonScopecreepTests arepainful butnecessary

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