> For the complete documentation index, see [llms.txt](https://playbooks.equalexperts.com/remote-working/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://playbooks.equalexperts.com/remote-working/introduction/colocation-is-better.md).

# Agile Law

## Colocation is always better … stating the bleeding obvious?

Colocation is always better than remote working; it states it in the agile bible somewhere so it must be true.

There is an assumption that colocation is better. After all, in Kent Becks - Extreme Programming Explained the very first Primary Practice he lists is Sit Together.

> ***Develop in an open space big enough for the whole team**.*

There is surprisingly little scientific evidence on the effectiveness of co-location, which seems to be more assumptions than hard scientific facts. There are a few quality articles. The majority of the literature is based on case studies and anecdotes and shows little in the way of quality evidence. The rise of the new wave of tools, such as Slack and Zoom and more focused working practices aimed at working remote, are not featured in these studies.

![](/files/-M5Wgmq_UXS3UhLquhtD)

### But don’t worry, it isn't anti-agile

As Beck continues in his book he states:

> ***Does the practice of sitting together mean that multisite teams can't do XP? The simple answer is no; teams can be distributed and do XP. Practices are theories, predictions. "Sit Together" predicts that the more face time you have, the more humane and productive the project. If you have a multisite project and everything is going well, keep doing what you're doing. If you have problems, think about ways to sit together more, even if it means travelling."***

So the "agile law" isn't so strict. Beck calls out a key reason why sitting together is important;

> ***the more face time you have, the more humane and productive the project***

So we should look at the underlying components that go into effective collaborative working and see how technology and working practices can help.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://playbooks.equalexperts.com/remote-working/introduction/colocation-is-better.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.