Measure your team productivity
What is the productive team in IT ?
I believe, that if your team is productive, this means that you bring a value continuously on a high quality level.
Everyday I ask myself if our team is as productive as possible.
Maybe we are, but maybe not. Sometimes we miss deadlines, sometimes we have bugs, but we still do a good job and produce a lot of valuable features.
The best way to estimate something is to measure.
How to measure the productivity ?
Lines of code per day? – not very reliable measure (frameworks, different languages, etc.)
Story points per day? (very relative measure, which is different from team to team)
Functional points – it’s nightmare to estimate them
However why not just record a time you are spending for developing a new features, fixing bugs, testing and managing activilies (in case of ordinary software development project).
OK. So after some time we have got a statistics. This is nice, you have got some measure, which is quite objective.
According to Steve McConnell, reworking defective requirements, design, and code typically consumes 40 to 50 percent of the total cost of software development.
In our case we have got:
20% bug fixing
Based on this, I would say that our team is quite productive. Our projects are less buggy than average and we spend 70-80% of our time for delivering new functionality.
I think this is a quite simple, quick and reliable way to understand if you perform well. However it may not work for your team.
So let’s define some criteria for the project:
1. 5-7 team members
2. It’s new product development or few features for existing product (not support)
Now we see that we are quite productive. What else we can do here?
We can outline what factors are important for the productive team.
I will write about this later.