As part of the Scrum.org webinar “Ask a Professional Scrum Trainer - Martin Hinshelwood - Answering Your Most Pressing Scrum Questions” I was asked a number of questions. Since not only was I on the spot and live, I thought that I should answer each question that was asked again here, as well as those questions I did not get to.
In case you missed it, here is the recording of yesterday’s Ask a Professional Scrum Trainer webinar with Martin Hinshelwood! Watch here: http://ow.ly/ijiM50vwEkD
>>I am interested to hear your perspective about collocation. There’s a spectrum of opinions, it seems, from “Distributed teams and remote-only teams are the way of the future” to “The most effecient and effective method of communicating to and within the development team is face to face”. My personal experiences and I suggest the vast majority of data indicate collocation is optimal. I’d go so far as to say that collocation is ’empirically’ best – in particular if/when a team is suffering communication challenges. Yet The Scrum Guide(tm) doesn’t take a definitive position on this issue. What’s your position as a PST? What’s your advice to teams?
Lets first define what collocation is:
Collocation is a complimentary agile practice where all members of the same Scrum Team work on a daily basis in the same room, within visual sight of each other. -MrHinsh
You may argue with my definition, but thats what I am going with and we should note that its a complimentary practice and not a core practice. That is, its not required to be agile or to do Scrum. However I believe that it is a very rare situation that would result in a distributed Scrum Team to become a high performing Scrum Team. I’m defiantly not saying that it cant happen, I have heard tell of highly efficient and value orientated Teams that were distributed. I just cant help but thing that is they were that awesome distributed, how much more amazing would their output have been if they had been collocated.
While collocation is not required, it is highly recommended especially for new teams. The practice of sitting together, solving problems together, and supporting each other is something that humans need in their lives. Its important for our physiological and psychological wellbeing. We need to interact.
You should head over to Scott Hanselman blog and read about the plight of the remote worker from someone whom has been able to leverage technology significantly. As you read I think you will see, as I did, that this is a lot of effort trying to mimic that personal interaction and physical presence. So while remote working is certainly a possibility, it requires the judicious use of right technology to make it work.
Ultimately for small organisations with few developer’s you may have no choice but to be remote, its not ideal, but we can make it work. I believe that ideally we should be collocated at least within the same Scrum Team. We can have a number of Scrum Teams that are not in the same location as long as the members of each Scrum Team are collocated.

Microsoft has been studying the value of colocation and team rooms for quite some time and its interesting that they have been investing billions of dollars to remodel all of their engineering spaces into fully functional Team Rooms. Every team room is out of earshot of all the others, it has space for up to 12 team members, and has both a video conferencing room that can hold everyone, and two breakout rooms. These rooms are only for the team and are not bookable by anyone else.
This type of space provides not only a level of Focus, but a level of self, of ownership, that is just not posible in a shared space. These teams fell like they are valued by the organisation, and feel empowered to take control of their own culture.
Its clear from the data that collocation is best, but its just not always available based on company culture and how things are organised. If you are unable to be collocated then the role of the Scrum Master is to work to minimise the negative impact of the team while working on the organisational impediments that resulted in the problem in the first place. Hopefully we will all be working in team rooms in the future.
While there are no right answers there are some answers that are better than others. For your given situation select the most right answer, and iteration to the best version of it.
Smart Classifications
Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.
What to read next
How do you handle conflict in a Scrum Team?
Guidance on resolving conflict in Scrum Teams, including facilitation techniques, escalation steps, and the Scrum Master's role in fostering …
How do you incorporate a Design Sprint in Scrum?
Explains how to integrate Design Sprint activities within Scrum by embedding design and UX work into regular sprints and backlog refinement, …
Should the Scrum Master always remove impediments?
Explains when a Scrum Master should remove impediments, focusing on team self-sufficiency, true impediments, and supporting team growth …
What's the best way to work around multiple PO?
Guidance on addressing issues with multiple Product Owners in Scrum, highlighting the need for clear backlog ownership and accountability to …
No Estimates and is it advisable for a Scrum Team to adopt it?
Explores whether Scrum Teams should adopt No Estimates, comparing estimation methods, team maturity, and metrics like cycle time, …
Mastering Remote Work: Key Insights for Agile Teams to Thrive in a Digital World
Practical strategies for remote Agile teams, covering communication, tool selection, value delivery, team dynamics, gamification, and …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
The Definition of Done is a Commitment to Quality
Defines the Definition of Done in Scrum as a clear, shared standard for quality, ensuring increments are releasable, transparent, and …
Why Your Definition of “Done” Is Holding Back Quality, Agility, and Trust, And How to Raise the Bar
Is your team’s “done” really done? Discover how a clear, objective definition of done boosts quality, agility, and trust in product …
Acceptance Criteria vs Definition of Done: Why Getting This Right Builds Trust and Delivers Quality Faster
Stop confusing acceptance criteria with definition of done, learn the crucial difference to boost quality, speed, and trust in your agile …
How to Evolve Your Definition of Done: Start Small, Grow Smarter, and Build Lasting Momentum
Unlock a smarter Definition of Done, start small, evolve standards, and build team momentum without overwhelm. Discover how progress drives …
Why Most Transformations Fail Without Honest Conversations
Most transformations fail without open, honest conversations that address real issues, making transparency and tough dialogue essential for …
Why Your Definition of Done Is the Secret Weapon for Real Business Impact and Agile Growth
Transform your definition of done into a strategic advantage, deliver real value, reduce risk, and drive business impact with every sprint.
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Kendall Guide - A System of Work for AI Adoption
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Estimating Better in an Overloaded System Is a Poor Man’s Strategy
High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …