Resources

I often hear people talk about “adding resources” to a software team or project, and I really don’t like it. 


And there’s two reasons why I don’t like it. 

Firstly, we’re talking about people. Sentient, caring, decent people. People aren’t resources. People should be treated with dignity and respect. And calling someone “a resource” is not a nice thing to do. I am not a number...

But secondly, the underlying assumption with “adding resources to a team” is that “more resources equals more productivity”. And that’s problematic. Teams are complex systems, and adding more people to a team, disrupts the team. It sends the system off on a new trajectory. And it might never make it back to where it was. So simply adding people to a team can completely change the team dynamic, and can completely change the team’s performance. 

Another problem with the assumption is the idea that new team-members just need to be “brought up to speed” in order to be productive. But the mental models that we build up about our code are complex in themselves, and very difficult to describe to anyone else. And, because any new team-members will have a much lower-quality mental model of the code’s behaviour, they will make much lower-quality changes to the code. 

Adding people to the team means that existing team members have to try and convey their mental models to the new people. And they have to guide the new team members as they make what would be basic mistakes to the original team members. 

And that of course requires good conversations, trust between team members, respect and kindness. And these all take time to build up. High quality social interaction is complex and takes time to build up. Team members need to build up a shared context to allow such communication. 

Even worse, as the team grows, the number of social interactions grows rapidly, and the chances of a common understanding or context decreases rapidly. 

So, don’t assume you can disrupt a human social group and achieve any predictable results, let alone an increase in productivity. 

Comments

Post a Comment

Popular posts from this blog

SoCraTes UK 2024 trip report

In September 2024 I attended my second SoCraTes conference, and once again, it was enlightening and fun. There are two formal parts to the conference - a training day, and then two days for the unconference. I say formal parts, because there are plenty of informal sessions as well. One of the great things about SoCrcaTes is that we all stay at the same hotel, so there is loads of opportunities for social interaction. You meet people at breakfast, you maybe go for a walk with other people, there are board games and music sessions in the evenings... It's a strange mixture of really intense and very relaxing! There's a lovely Italian Garden at the hotel, which is a very nice place to sit and chat: SoCraTes has a pretty strong XP focus, but there are plenty of non-technical discussions and workshops too.  The day before This year, the conference was at Milton House Hotel just outside Didcot in Oxfordshire. So on the day before the conference, I took the train from Edinburgh to Lon...
Read more

We always start from where we are

Image
Earlier on in this year, I had a really interesting discussion online with Duncan Hothersall about Scottish Independence, and Brexit. I support independence, and Duncan very much doesn't. Scotland is currently about evenly split between supporters and opponents of independence, with a small number of hardcore unionists and nationalists on either side. But many people are in the middle, and weigh up the decision based on the perceived pros and cons. In itself, this disagreement between Duncan and myself is interesting. We share a similar world-view and similar hopes for the future. We agree in many ways on the kind of future we would like to see. But we disagree on how we want to get there.  This is of course a common pattern. We often share a purpose with other people, but we disagree on the tactics or maybe even the strategy for how to achieve it, and there is a wealth of literature on how to resolve such disagreements.  But what I found fascinating was how we both responded...
Read more

Naming things and Cunningham’s Law

Naming things is hard.  Naming things is very hard.  And, in software, we often want to name things when we know least about them. We create a variable that we plan to use later. What should it be called? How should it be used? We only have a vague plan at this point. And plans, of course, can change.  In my mob, we sometimes struggled to name things. And we would then fall into long discussions about what to call a variable. This often felt like bike-shedding, but we wanted a good name, so we carried on talking.  Then one day, we came up with a new plan. If we couldn’t name something within ten seconds, the person at the keyboard would just hit the keys at random and produce a gibberish name.  We would then use this unpronounceable name in the code, and move on.  And, as we moved on, we would have to talk about the unpronounceable thing. So we call it by what is was doing, by how we were using it. And, often, the name would then become apparent.  By ...
Read more