
doi: 10.1109/seaa.2011.71
Software effort estimation is critical for resource allocation and planning. Accurate estimates enable managers to distribute the workload among resources in a balanced manner. The actual workload of developers may be different from the values observed in project management tools. In this research, we provide a summary of our experiences regarding: a) effort estimation activities, b) the developer workload distribution through churn data and c) a method of using churn data to track estimation process. Our experience report depends on our collaborative work with our industry partners operating in various domains in Turkey. As a result, we observe that effort estimation is taken as an important topic. However, there is a large space for research to transfer the ad-hoc methods employed in industry to empirical ones. Interestingly, we observe that resource allocations based on initial estimates/plans do not conform to actual values. The common characteristic of developer contribution in different projects is: More than 80% of edits in code are performed by a small number of developers.
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 10 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Top 10% | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
