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