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

Capturing decisions and those involved

  • December 8, 2023

My role has changed recently to include another team. This has also included more interaction with other areas of the business and also the management team.


Read More

Preparation meets opportunity

  • June 13, 2022

Another podcast … I was listening to Guy Raz interview General David Petraeus on the “Wisdom from the top” podcast. Towards the end he made the observation that luck is where preparation meets opportunity. This implies the more prepared you are then the more “lucky” you will be when opportunities arise.


Read More

Tackle the difficult problems first with #MonkeyFirst

  • May 23, 2019

I was listening to the audiobook for “Questions Are the Answer” by Hal Gregerson and it mentioned an approach used by the X lab at Alphabet nicknamed “MonkeyFirst”.


Read More