Stomping Out Software Rework
There are two definitions of rework in software projects…the good and the bad:
Rework, The Good: redesign, reimplementation, retest of preexisting software during enhancement.
Rework, The Bad: having to redo the same work multiple times due to errors or lack of review. Rework is doing the same thing over again, excluding refactoring which is done to make software more maintainable.
Galorath has been working hard at reducing the bad rework over the past year. This process has involved more detailed reviews of user interface and other critical items  during requirements and design. For example, today I sat in a review of an enhanced dialog box for a major SEER function. The review, and the associated changes took 4 people an hour each. This is the 2nd review.  The first setup the details of the requirements.  Some would say that is a lot of time to spend on a single dialog box (even a critical one). But the dialog box is better (yes we have criteria for better) than it was as the review started. So two wins: 1) there will not be rework when the dialog box is deployed and 2) the users will get a better experience, reduced technical support and easier training.Â
The 8 hours total of review will pay back many times over.
Thank you for reading “Dan on Estimating”, if you would like more information about Galorath’s estimation models, please visit our contact page or call us at +1 310 414-3222.
Related Posts Computer Generated
Comments
Leave a Reply