What is your perspective on collocation?

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!

Lets first define what collocation is:

You may argue with my definition, but that’s 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 possible 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.

Originally published at https://nkdagility.com on October 21, 2019.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Martin Hinshelwood

Martin Hinshelwood is a Professional Scrum Trainer and Microsoft MVP. He has been Consulting, Coaching, and Training in DevOps & Agility since 2010.