16 September 2010

Challenge your assumptions on the cost of quality

The usual thinking is that the earlier your find a bug the cheaper it is to resolve, and that the cost of defect remediation increases exponentially over the product life cycle.

Don't buy that at face value.  

Architecture, the team's capability and the tools and systems the team use will all affect this model.  It's not infeasible that the cost of remediating a bug in production is less than avoiding it in requirements discovery.

In fact, why don't you start measuring this today?  how much time is spent on each aspect of the product delivery process, and what does each cost in terms of rework?

1 comment:

  1. I agree. It is a misstatement of the process.

    Bugs aren't found in requirements. Bugs are failures to meet requirements, or just bad coding.

    What is bad in requirements is missing them. Or spending time on the wrong requirements based on bad planning or goal setting. Systems that implement requirements that don't help the business don't have bugs, they are just the wrong systems.