Iterative Rework: The Good, the Bad, and the Ugly

Authors:
Richard E. Fairley;Mary Jane Willshire
Affiliations:
Oregon Health and Science University;Colorado Technical University
Venue:
Computer
Year:
2005

Citing 4
Cited 5

Software Process Evolution at the SEL

IEEE Software
Refactoring: improving the design of existing code

Refactoring: improving the design of existing code
Software Defect Reduction Top 10 List

Computer
Process Improvement and the Corporate Balance Sheet

IEEE Software

Overseas development for a major U.S. eCommerce website

Proceedings of the 28th international conference on Software engineering
To pull or not to pull

Proceedings of the 24th ACM SIGPLAN conference companion on Object oriented programming systems languages and applications
The effect of moving from a plan-driven to an incremental software development approach with agile practices

Empirical Software Engineering
Towards quantitative software reliability assessment in incremental development processes

Proceedings of the 33rd International Conference on Software Engineering
Assessing requirements compliance scenarios in system platform subcontracting

PROFES'06 Proceedings of the 7th international conference on Product-Focused Software Process Improvement

Quantified Score

Hi-index	4.10

Visualization

Abstract

In software development, some rework is both inevitable and beneficial. But how much is too much and how little is too little? Understanding the nature of rework and why it occurs can help answer these questions.