[SystemSafety] Another question

[Derek M Jones]

Steve,

> In my own work with software organizations I look at “Rework Percentage” (R%): the percent of project labor hours that are spent later fixing things that were earlier claimed to be correct but found to be deficient. Estimates of rework normally average around 50%. I’ve actually measured R% in five different software organizations:
> 
...
> All for a weighted average of about 62%.
> 
> This means that rework is the single largest contributor to project cost and schedule, and it is bigger than all other contributors combined.

So what, it may be the cheapest option.

Perhaps releasing an initial version was the cheapest and fastest
way of flushing out the unknowns.

You cannot claim that just because some factor contributed the
largest amount, that this was somehow bad.  What were the
alternatives?

-- 
Derek M. Jones           Software analysis
tel: +44 (0)1252 520667  blog:shape-of-code.coding-guidelines.com