Numbers for managing teams

Sometimes you come across an article that makes you think. The article, Numbers To Know For Managing Software Teams, made me do that.

My daytime role involves managing helping a team of developers to deliver a great product. The article lays out a number of guidelines for how often something should happen. I don’t necessarily agree with all of them but it is an excellent thought exercise to look at what you do and come up with your own set of guidelines.

For example,

7 - the number of days before a new hire should have merged a pull request

We try and achieve this within 2-3 days.

5 - the number of comments on a document before you should ask to talk about the issue

I thought this was an interesting rule of thumb. So much time and effort could potentially be saved by doing this.

Links

Numbers To Know For Managing Software Teams

Related Posts

Beware of the normal

It is easy to take things and people for granted.


Read More

Creativity modes

I recently discovered the Huberman Lab podcast so I have been working through the back catalogue. I was listening to one on creativity and mentioned that creativity is effectively taking existing elements and rearranging them in novel ways. It highlighted that there are two parts to creativity - creating/discovery and linear/implementation.


Read More

Alarms lost in the noise

Adding an alert or alarm for a situation you need to monitor should be a good thing but sometimes, depending on how it is done, it can actually make things worse or at a minimum not work as expected.


Read More