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

Random Posts

The fastest way to switch Gmail accounts on Android phones

Using Gmail on Android it is possible to support multiple email accounts. The normal way you can change which account you are looking at is by pressing on the account picture in the top right hand corner and then selecting the user.


Read More

Avoiding regrets

When my daughter was at nursery I missed a show she was in. Unknown to me, she had the leading role and I missed it because of a work meeting.


Read More

Lex, an AI assisted editor

Lex.page was one of the first AI assisted editors available.


Read More