Agile Colocation

Agile ColocationI was very interested to read this post about agile colocation on Artem Marchenko’s Agile Software Development blog. The comments are also very interesting.

As always, I don’t think the colocation debate is black and white…

I’ve read plenty of articles and blog posts about the merits of colocation. I’ve also read lots about how colocation is an essential ingredient of agile development. And I’ve read some very good counter-arguments explaining how agile can work – and is working – with teams that are not located together and even working across borders.

I think the debate, as with most things depends on your circumstances.

In our case we have business teams in multiple locations. So is it best to locate the associated development teams in the same building as the business units, or in a central development group colocated with their technical peers and other people of a like mind?

There is certainly a case for colocation with either group, but they can’t be in two places at once so we have to choose!

In situations like this, I think it comes down to which group of people is most valuable to collaborate with most frequently.

If you have an established product or business in a BAU (Business-As-Usual) situation, but a development team whose development practices are not well established, I would suggest that ongoing product development is best placed near other, more established development teams, where good development practices and experience can be shared amongst peers.

If, on the other hand, you have an established development team with good development practices, performing well and delivering what’s expected, but a product or business unit that is not in a stable situation (e.g. new product development, competitive threat, major problems, etc), I would suggest that colocation with the Product Owners is much more important. In this case, active user involvement is imperative, in order to provide extra visibility, get very regular feedback and customer insight, and be able to respond in Sprints accordingly.

In any event, I do think distance adds to the compromise, wherever you are permanently located. I’ve made comments before about this in relation to Agile India. If the opportunity for face-to-face communication is virtually nil, then I think the compromise is a really big one.


One Response to “Agile Colocation”

  1. Artem Marchenko says:

    IMHO, most of the time the most efficient way to develop software is to colocate a small cross-functional team together with the customer. The problems start arising when you have to compromise. E.g. if you just have to work with the offshore team or if the project is clearly too big for 5-10 people. And if you have to compromise, well.. then you have to compromise :)

Leave a Reply

What is 10 + 1 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)

There are 101 ways to approach anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”