How do you preserve team cohesion as you scale?
John Van Wagenen May 16 '17
When I started at the company I currently work for, we had about 60 individuals in the department. That's including management, QA, Developers, etc. When someone new joined the company, it was pretty easy to at least know who they were and what role they filled. Often we got to know them pretty well within a few weeks of them starting.
Since then, the company has grown. We've added new roles, adopted the Scaled Agile Framework, and grown our existing teams. Now we're just north of 100 individuals in the department. When someone new starts, those outside the team they join might not know whether they're developers or quality assurance or product owner or scrum master for a few weeks at least. It seems to be harder to get to know our coworkers now.
This seeming decline in cohesion and communication has been on my mind a bit recently. I've read a few things about it and there seems to be some really cool things that other companies do to help combat this. So, I'm curious, how do you maintain team and department cohesion as you scale? What have you seen work? Do you think it's important to have cohesion outside of individual teams?