2 exercises — async-first, working agreements, follow-the-sun, DACI, and other distributed team concepts.
0 / 7 completed
1 / 7
A new colleague mentions they're uncertain about your team's communication style. They ask about "async-first" and "working agreement." Which definition is most accurate?
Option B gives accurate definitions of both terms:
Async-first: • Default communication channel: written, persistent, non-real-time (Slack, Notion, GitHub, Jira comments) • Meetings are not banned — they're reserved for things that genuinely benefit from synchronous interaction: creative brainstorming, sensitive conversations, live debugging • The opposite of "async-first" is "meeting-first" — where the default for every question is scheduling a call • Benefit: allows distributed teams across multiple timezones to function without everyone being online simultaneously
Working agreement (also: "team charter", "team norms document"): • Typical contents: core hours (UTC time window when everyone is expected to be reachable), async response time SLA ("respond within 4h during working hours"), decision-making process (DACI, RFC process), code review norms, communication channels by topic (production issues → #incidents; social → #random), PTO communication process • It's not a legal document — it's a living practice guide the team owns and updates • It eliminates ambiguity for new team members and prevents recurring friction
Overlap hours / core hours: The daily time window when all team members across timezones are expected to be reachable. Small teams might have 2h overlap; larger teams with more distributed members sometimes have zero natural overlap.
2 / 7
Your team lead mentions the team uses a "follow-the-sun" model and a "DACI" framework for decisions. You're new and need to explain these to a vendor. Which explanation is correct?
Option C contains accurate definitions of both terms:
Follow-the-sun model: • Used by teams spread across 3+ timezones covering roughly 8-hour working day segments • When Singapore finishes the day, they hand off to Berlin; Berlin hands off to San Francisco • Enables near-continuous development or support coverage without overnight shifts • Requires excellent async handoff discipline (see: async-written-updates exercises) • Common in: global SRE teams, 24/7 customer support, large open source projects
DACI framework: • Driver — owns the process: gathers input, sets timeline, writes the decision doc. Not necessarily the decision-maker. • Approver — has final sign-off authority. One person (avoid multiple approvers — that creates deadlock) • Consulted — subject matter experts whose input is needed before deciding • Informed — told about the outcome but not consulted
Related decision frameworks: • RACI (Responsible, Accountable, Consulted, Informed) — similar, used for task ownership • RFC (Request for Comments) — asynchronous written proposal process common in open source and engineering orgs • ADR (Architectural Decision Record) — log of technical decisions with rationale, alternatives considered, and consequences
3 / 7
Sarah from the Berlin team just posted this comment on your PR: 'This change seems a little opaque. Could you add more context about why you're using this approach?' What does 'opaque' most likely mean in this situation?
'Opaque' in technical communication often refers to something that is unclear or difficult to understand. While the other options relate to potential issues with the code itself (performance, aesthetics), 'opaque' specifically highlights a lack of explanation – a key concern when discussing remote collaboration and ensuring everyone understands the rationale behind decisions. It's vital to address this immediately to avoid misunderstandings.
4 / 7
Mark, during your daily standup, says: 'I'm blocked on getting feedback from the QA team. They're currently running a regression test and haven't flagged any critical issues.' What does Mark likely mean when he uses the phrase 'running a regression test'?
A 'regression test' refers to a specific type of software testing where the QA team re-executes existing tests after code modifications. This is done to verify that new changes haven't inadvertently broken previously working functionality – a core concept in maintaining stability across distributed teams and releases. Mark's statement indicates this process is actively underway, causing his block.
5 / 7
You're reviewing a PR that introduces a new API endpoint for user authentication. The response from the server contains the following JSON: `{"status": "200", "data": {"token": "abcdef123456"}}`. What does the 'token' field represent in this context?
In API responses, 'token' typically signifies a temporary credential issued after successful authentication. This token allows the client to make subsequent requests without re-entering credentials. It's crucial for secure communication in distributed systems, where managing user sessions remotely is essential. The 'status' field confirms success.
6 / 7
David from the London team sends you this Slack message: 'Hey @everyone, just pushing a fix for that weird edge case we saw in the payment processing module. Let me know if you spot any issues!' What does David likely mean by 'edge case'?
An 'edge case' refers to a less common or exceptional situation that is difficult to predict or test for thoroughly. It represents a scenario outside of typical usage patterns – often highlighting areas where the code might fail unexpectedly, especially when teams are working remotely and testing coverage may be limited. David's message indicates he has identified and addressed one such case.
7 / 7
Your team is adopting a new workflow that emphasizes asynchronous communication. You need to explain this to a junior developer who's unfamiliar with the concept. Which of the following explanations would be most effective?
'Asynchronous communication' is fundamentally about decoupling responses and allowing individuals to engage with information at their convenience. This contrasts sharply with synchronous methods (like real-time calls or instant messaging), which demand immediate attention. The key here is the *lack* of a required response – enabling flexibility for distributed teams working across different time zones.
What will I practice in "Distributed Team Vocabulary — Remote Communication Exercise"?
This is a Remote & Async exercise set. It walks through 7 scenario-based multiple-choice questions built around real usage of remote & async terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 7 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the remote & async vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more Remote & Async exercises?
See the Remote & Async exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — remote & async vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.