Atlas › 21 Communication & Stakeholder Management › Remote and Distributed Teams☰ Read as one page
Remote and Distributed Teams
7.1QA in the Async-First WorldRemote work has fundamentally changed how QA engineers operate. When you cannot tap a developer on the shoulder to discuss a bug, when your…7.2Async Communication Best Practices for QAWrite as if the reader will see your message 8 hours from now, in a different timezone, with no ability to ask clarifying questions. Every…7.3Timezone Management for TestingQA testing often depends on other people's work -- a developer deploying a fix, DevOps updating an environment, a product owner clarifying…7.4Documentation-First CultureIn a co-located team, tribal knowledge -- unwritten rules, known quirks, informal agreements -- spreads through conversation. In a remote…7.5Tools for Remote QA CollaborationChannel structure for QA teams:7.6Maintaining Team Culture and Knowledge Sharing RemotelyRemote QA engineers are at high risk of isolation because testing can be a solitary activity. Combat this intentionally:7.7Onboarding New QA Team Members RemotelyRemote onboarding is harder than in-person onboarding because new team members cannot absorb context through osmosis. Everything must be…7.8Hands-On Exercise1. Audit your team's async communication: pick 5 recent bug reports and evaluate whether they would be understandable to someone in a…