ACM Home Page
Please provide us with feedback. Feedback
Mining software effort data: preliminary analysis of visual studio team system data
Full text PdfPdf (349 KB)
Source
International Conference on Software Engineering archive
Proceedings of the 2008 international working conference on Mining software repositories table of contents
Leipzig, Germany
SESSION: Understanding and infrastructure table of contents
Pages 43-46  
Year of Publication: 2008
ISBN:978-1-60558-024-1
Authors
Lucas Layman  North Carolina State University, Raleigh, NC, USA
Nachiappan Nagappan  Microsoft Corporation, Redmond, WA, USA
Sam Guckenheimer  Microsoft Corporation, Redmond, WA, USA
Jeff Beehler  Microsoft Corporation, Redmond, WA, USA
Andrew Begel  Microsoft Corporation, Redmond, WA, USA
Sponsors
SIGSOFT: ACM Special Interest Group on Software Engineering
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 11,   Downloads (12 Months): 85,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1370750.1370762
What is a DOI?

ABSTRACT

In the software development process, scheduling and predictability are important components to delivering a product on time and within budget. Effort estimation artifacts offer a rich data set for improving scheduling accuracy and for understanding the development process. Effort estimation data for 55 features in the latest release of Visual Studio Team System (VSTS) were collected and analyzed for trends, patterns, and differences. Statistical analysis shows that actual estimation error was positively correlated with feature size, and that in-process metrics of estimation error were also correlated with the final estimation error. These findings suggest that smaller features can be estimated more accurately, and that in-process estimation error metrics can be provide a quantitative supplement to developer intuition regarding high-risk features during the development process.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
 
2
 
3
 
4
 
5
 
6
 
7
 
8

Collaborative Colleagues:
Lucas Layman: colleagues
Nachiappan Nagappan: colleagues
Sam Guckenheimer: colleagues
Jeff Beehler: colleagues
Andrew Begel: colleagues