How to estimate the contribution of an individual to a software project?

Posted by Amit Kumar on Stack Overflow See other posts from Stack Overflow or by Amit Kumar
Published on 2010-03-13T09:41:35Z Indexed on 2010/03/13 9:45 UTC
Read the original article Hit count: 450

I work on a software project and would like to estimate the percentage out of the total contribution that I have put in the development of the software. Is there some tool doing this? Such a tool can be useful for appraisals or negotiations, for example. After all, we work for money (yes, not only money, put the point remains). I think there is enough hand-waving for the most important things.

The estimation is very subjective (at least to me now) but I do not know of any tool that provides even a subjective estimate. I know of Sloccount that spells out the total effort using the lines of code but not on per-developer basis.

My idea of an ideal tool for this purpose would:

  • measure the complexity of the code (more complex is more effort, but more effort is not necessarily more contribution)
  • measure the decomposibility/flexibility of the software (more decomposable is better)
  • how much library code is used -- using library code speeds up the development process, increases the associated risk and requires the developer to know from before or learn about the library.
  • be intelligent enough to differentiate between "who wrote the code", "who copied the code" and "who indented the code".

It is difficult to differentiate between the complexity in the implementation and the intrinsic complexity of the problem. Perhaps a comparison can be made with an equivalent open source counterpart if there is, or for each submodule separately.

If there is no such tool, is there no merit in having such a tool? Or do you believe in "I do work, I do not measure"? It takes time after all. Perhaps the project manager should do this estimation continuously, say, weekly. Are there any standards? Yes, standardization is difficult because every project has a different goal, but difficult does not mean it is not useful.

© Stack Overflow or respective owner

Related posts about software-engineering

Related posts about software-estimation