See how Alex worksWork with Alex
All frameworks

Framework

Scrum in Distributed Companies: What Survives, What Breaks, What to Adapt

"Scrum provides an empirical control loop; distributed companies demonstrate several ways to make goals, decisions and feedback explicit. Compare the purpose of each event with the coordination it provides. Async alternatives are adaptations to evaluate, not proven universal replacements for Scrum events, roles or co-location."

A source-backed comparison of Scrum and distributed operating practices. Distinguishes the official Scrum Guide from proposed adaptations, corrects Sprint timeboxes, and bounds what company examples can establish about cadence, retrospectives and scaling.

By Alex Karasyov — Operating consultant for product & engineering teams

Last reviewed September 12, 2026

Thesis

The official Scrum Guide remains the November 2020 edition as of this review. It specifies Sprints of one month or less and identifies transparency, inspection and adaptation as its empirical pillars. Its events have defined purposes; the Guide does not require story points or velocity. (Guide, official version index)

[Inference — comparison of operating models.] Distributed companies such as 37signals, GitLab, Linear and Todoist use written artifacts, explicit goals and feedback in different combinations. These similarities are useful comparisons; they do not establish that the companies secretly run Scrum or that their mechanisms are interchangeable with its accountabilities and events.

Scrum.org publishes remote guidance for individual events. A separate January 2026 Scrum Guide Expanded identifies itself as an adaptation of the 2020 Guide, not a replacement jointly issued by the original authors. This page likewise distinguishes its proposed adaptations from official Scrum. (Remote guidance, Expanded document)

Symptoms

[Inference — diagnostic questions, not measured prevalence.] Review an event when its coordination cost exceeds the value participants can identify:

  1. Does the Daily Scrum inspect progress toward the Sprint Goal, or has it become a general status meeting?
  2. Can people in every time zone participate without repeatedly working outside agreed hours?
  3. Does the Sprint Review produce stakeholder feedback that changes the plan?
  4. Can people raise difficult issues in the retrospective, and do agreed improvements get followed up?
  5. Are estimates informing decisions or being treated as performance targets?
  6. Are the Scrum Master’s responsibilities clear, assigned and supported?

Cucolaș and Russo’s study reports challenges with remote communication and retrospective engagement. It does not establish that every remote retrospective fails or that prior offline contact is necessary. (Study)

Root Causes

The purpose and the meeting format can be confused. Scrum.org’s distributed-event guidance discusses preparation, facilitation and feedback. [Inference — application guidance.] Evaluate whether the chosen format supports inspection and adaptation before changing it. Removing a live event without preserving its purpose can leave a coordination gap. (Planning guidance, review guidance)

Evidence about a whole framework cannot isolate an individual role. The distributed-Scrum meta-analysis studies project-level outcomes. It does not establish that a dedicated Scrum Master is redundant below 50 people, or that a documentation system substitutes for that accountability. (Meta-analysis)

Scale is not a controlled comparison. LeSS continues to advocate co-location while acknowledging distributed implementations. GitLab and Automattic demonstrate that large distributed organizations are feasible. They do not directly test LeSS against comparable co-located organizations or establish that co-location offers no collaboration benefit. (LeSS, GitLab, Automattic)

What Companies Get Wrong

[Inference — application guidance.]

  • Moving every event online without checking its purpose. Reassess preparation, participation, decisions and follow-through, not just the conferencing tool.
  • Calling a written check-in unchanged Scrum. A replacement for the prescribed Daily Scrum is an adaptation; document which inspection and coordination functions it preserves.
  • Treating product configuration as company practice. Linear’s configurable cycles and optional cooldowns do not establish a mandatory internal one-to-two-week cadence. (Product documentation)
  • Using company size to declare LeSS refuted. Feasibility evidence does not settle comparative effectiveness. (Current LeSS position)
  • Making offline trust a prerequisite for candor. A distributed retrospective may be harder when participants lack trust. Evaluate relationship-building and facilitation; prior in-person contact is not established here as a necessary condition. (Study)

What Works Instead

Preserve the control loop

The Guide defines the Sprint Goal, Definition of Done, Product Owner accountability and inspection/adaptation events. [Inference — application guidance.] Make the relevant goals, quality expectations, ownership and feedback visible before reducing the meeting load. Similarity to another company’s practices does not prove that a specific Scrum commitment or accountability is present there. (Guide)

Evaluate adaptations explicitly

  • Daily inspection. [Inference — proposed experiment.] Where time zones make a live check-in costly, test written progress and blocker updates with clear response expectations. This departs from the prescribed Daily Scrum. Keep deliberate live coordination where useful; GitLab permits synchronous starts for strategy, trust-building, disagreements and difficult context, as well as escalation after three exchanges. (Scrum.org guidance, GitLab)
  • Sprint Planning. Prepare candidate goals and backlog context asynchronously. [Inference — facilitation recommendation.] Consider a four-hour maximum for a two-week Sprint and shorten it when preparation permits. The Guide specifies an eight-hour maximum for a one-month Sprint and says shorter Sprints usually have shorter planning events; it does not give every Sprint an eight-hour allowance. (Guide, preparation guidance)
  • Sprint Review. [Inference — proposed experiment.] Use recorded context and written feedback to prepare stakeholders, then reserve live discussion for questions that benefit from it. Assess whether the result informs product decisions. (Review guidance)
  • Sprint Retrospective. [Inference — facilitation hypothesis.] Invite written input in advance and test facilitation that supports candid discussion. Social calls, written interaction and in-person contact are possible relationship investments; the evidence does not require annual travel as a condition for an effective retrospective. (Remote retrospective guidance, retreat evidence)
  • Sprint length. The official limit is one month or less. [Inference — application guidance.] Choose a cadence appropriate to feedback, dependencies and release needs. The reviewed company cases and sprint-length research do not establish a universal one-to-two-week optimum for distributed teams. (Guide, sprint-length study)
  • Roles and scaling. [Inference — application guidance.] Decide how accountabilities will be staffed from the actual work. No sub-50-person redundancy rule is supported here. Compare scaling frameworks’ assumptions with your organization; LeSS’s co-location preference is a fit consideration, not evidence that another framework will automatically perform better. (LeSS, Scrum@Scale)

Company Evidence

37signals / Basecamp documents six-week build cycles followed by two-week cooldowns, shaping and appetite-based scope. These provide a comparison with Scrum planning, not proof that Shape Up implements Scrum accountabilities. (Handbook, Shape Up)

GitLab reported 2,580 team members in 60 countries at January 31, 2026. Its handbook describes week, month, quarter, year, three-year, ten-year and thirty-year horizons, with adjacent horizons roughly three to five times apart. This demonstrates a documented planning system at scale, not a controlled test of LeSS. (Filing, cadence)

Linear describes continuous development of candidate projects prioritized against customer demand, revenue impact and quarterly goals in its October 2025 planning account. Its public Method and configurable product cycles are distinct from verified company-wide rituals. The August 2026 $99 million employee tender was secondary liquidity at a $2.5 billion valuation, separate from its June 2025 Series C. (Company planning, product cycles, tender)

Todoist (formerly Doist) currently lists 108 people in 38 countries. Its September 2022 accountability article describes 1–5-person DO squads, objective cycles of one to six months, regular manager 1:1s and retrospectives. Current onboarding still references DOs and cycle planning, but the exact present cadence is not publicly established. It is inaccurate to describe this as no meetings or no published cycle system. (About, 2022 system, onboarding)

Automattic lists 1,422 people on its current About page and uses P2 alongside Linear, private chat rooms and Slack. This is a current snapshot, not a count verified immediately after the April 2025 restructuring. Large distributed operation demonstrates feasibility without measuring the comparative benefit of co-location. (About, working practices)

Founder Actions

[Inference — implementation guidance.]

  1. Review each event against its purpose for one cycle. Record decisions and improvements it produces, participation barriers and time spent.
  2. Prepare goals and decision context before planning meetings. Evaluate a shorter meeting on outcomes, not on a universal time target.
  3. Test one adaptation at a time. Document the accountability, artifact, feedback and escalation path it preserves.
  4. Improve retrospective facilitation and relationships without assuming that international travel is a prerequisite.
  5. Compare appetite-based scoping with the team’s existing planning method where useful. Shape Up is a documented alternative, not proof that estimates never help. (Shape Up)
  6. Choose roles and scaling practices by the coordination problem they solve. Do not use a company headcount cutoff or a comparison of unrelated companies as causal evidence.

Where This Framework Breaks

  • [Inference.] Incident response and other urgent coordination can require immediate live discussion; an async response window may add unacceptable delay.
  • [Inference.] Teams with substantial overlap may benefit from the canonical live events. Distribution alone does not justify replacing them.
  • [Inference.] Removing an event without maintaining its inspection, decision and feedback functions can reduce transparency.
  • The cases here largely concern software organizations. They do not establish comparative outcomes for every industry, company size or scaling framework.

Sources

Canonical Scrum:

  1. The Scrum Guide 2020 (Schwaber & Sutherland): https://scrumguides.org/scrum-guide.html
  2. Scrum.org — Remote Work and Scrum (Dave West, June 20, 2022): https://www.scrum.org/resources/blog/remote-work-and-scrum
  3. Scrum.org — Remote Agile (Part 5): The Remote Retrospective with a Distributed Team (Stefan Wolpers, April 14, 2020): https://www.scrum.org/resources/blog/remote-agile-part-5-remote-retrospective-distributed-team
  4. Scrum.org — Remote Agile (Part 6): Sprint Planning with Distributed Teams (Stefan Wolpers, April 19, 2020): https://www.scrum.org/resources/blog/remote-agile-part-6-sprint-planning-distributed-teams
  5. Scrum.org — Remote Agile (Part 7): Sprint Review with Distributed Teams (Stefan Wolpers, April 27, 2020): https://www.scrum.org/resources/blog/remote-agile-part-7-sprint-review-distributed-teams
  6. Scrum.org — Remote Agile (Part 8): Daily Scrum with Distributed Teams (Stefan Wolpers, May 4, 2020): https://www.scrum.org/resources/blog/remote-agile-part-8-daily-scrum-distributed-teams
  7. Scrum Alliance — How Agile Teams Overcome Obstacles Created by Distance (Jesse Fewell): https://resources.scrumalliance.org/Article/agile-teams-overcome-obstacles-created-distance
  8. Scrum@Scale Guide (Sutherland / Scrum Inc.): https://www.scrumatscale.com/scrum-at-scale-guide-online/
  9. LeSS Principles: https://less.works/less/principles
  10. LeSS — Notes on co-location and work from home (rules page): https://less.works/less/rules/colocation
  11. LeSS — Co-location still matters (Vodde, 2019): https://less.works/blog/2019/12/20/colocation-still-matters.html

Empirical:

  1. de Souza Santos, Ralph, Arshad, Stol-J (2023). Distributed Scrum: A Case Meta-Analysis. ACM Computing Surveys: https://dl.acm.org/doi/10.1145/3626519
  2. Cucolaș & Russo (2023). The impact of working from home on the success of Scrum projects. Journal of Systems and Software: https://pmc.ncbi.nlm.nih.gov/articles/PMC9684095/
  3. S&P Global action research (2025), Information and Software Technology: https://www.sciencedirect.com/science/article/pii/S0950584925000679
  4. Magalhães et al. (2025). A Delphi Study on the Adaptation of SCRUM Practices to Remote Work: https://arxiv.org/html/2503.21960
  5. Verwijs & Russo (2023). A Theory of Scrum Team Effectiveness. ACM TOSEM: https://dl.acm.org/doi/10.1145/3571849
  6. Digital.ai 18th Annual State of Agile Report (2025): https://digital.ai/press-releases/digital-ais-18th-state-of-agile-report-marks-the-start-of-the-fourth-wave-of-software-delivery/
  7. Anand, Kaur, Singh, Alhazmi (2021). Optimal Sprint Length Determination for Agile-Based Software Development. Computers, Materials & Continua, 68(3): https://www.techscience.com/cmc/v68n3/42509

Distributed-company operating evidence (cross-referenced from site profiles):

  1. 37signals — How We Work: https://basecamp.com/handbook/how-we-work
  2. 37signals — Shape Up: https://basecamp.com/shapeup
  3. GitLab — Cadence: https://handbook.gitlab.com/handbook/company/cadence/
  4. GitLab — Asynchronous communication: https://handbook.gitlab.com/handbook/company/culture/all-remote/asynchronous
  5. Linear — The Linear Method: https://linear.app/method
  6. Linear — Series C announcement (Building Our Way): https://linear.app/now/building-our-way
  7. Doist — How Doist Works Remote: https://doist.com/how-we-work/how-doist-works-remote
  8. Automattic — Expectations: https://automattic.com/expectations/

Scrum official version index: https://scrumguides.org/download

Scrum Guide Expanded — January 2026: https://scrumexpansion.org/scrum-guide-expanded/2026.1/pdf/scrum-guide-expanded.2026.1.en.pdf

GitLab current communication: https://handbook.gitlab.com/handbook/communication/

GitLab FY2026 filing: https://www.sec.gov/Archives/edgar/data/1653482/000162828026018731/gtlb-20260131.htm

Linear internal planning: https://linear.app/now/continuous-planning-in-linear

Linear product cycles: https://linear.app/docs/use-cycles

Linear August 2026 tender: https://linear.app/now/sharing-growth-with-the-people-building-linear

Todoist About: https://www.todoist.com/about-us

Doist September 2022 accountability: https://async.twist.com/accountability-remote-workers/

Todoist onboarding: https://handbook.todoist.net/s/6ca6f66e-2d02-4e05-b629-b1c772f5ff23

Automattic About: https://automattic.com/about/

Automattic working practices: https://automattic.com/how-we-work/

Inferences

  • Written preparation and explicit ownership may reduce unnecessary live coordination, but the effect should be evaluated locally.
  • A useful adaptation preserves a defined feedback and decision function; it does not earn credibility simply by reducing meetings.
  • Company examples establish possible operating choices. They do not isolate the effect of a Scrum role, prove a universal Sprint length or settle the comparative value of co-location.

Work with Alex

If your distributed team is reviewing its Scrum events, Alex helps leadership teams evaluate coordination needs and test adaptations with explicit goals, ownership and feedback.

frameworkscrumagileplanningasyncmethodology

Last reviewed September 12, 2026