in Software Engineering

Haste makes waste, part 157

In today’s episode, I lament when the rush to meet a deadline means that the software is not checked out sufficiently, and multiple problems/errors are discovered, most of which have to get fixed later. Sigh…

Sometimes there are business reasons for shipping something by a certain date. The cost of meeting that date, though, sometimes includes future payments to correct problems. There is no “one size fits all” answer to this topic, but the cost of corrections should be considered as part of the overall cost (unless schedule is king, which means resources will be made available to fix what needs to be fixed). Thoughts, anyone?

 

Write a Comment

Comment