It's Never Too Late!

It's never too late to what?

It is never, never, NEVER too late to scrap what you have done and start again. In fact, you will almost always have to redo some parts of any major project. It is also possible to predict what you will scrap, it will be one of the very early parts. Does knowing that you will have to go back and do some of the early work again help in any way? Yes, it does? There are a number of reasons why this knowledge can be useful;

• If you are expecting it to happen you may not compound the error by trying to 'make do', or ignore it, or blame the user, programmer, language, technology, etc. The quicker you deal with the problem once it becomes apparent, the better.

• Knowing that this is normal should stop the team from feeling guilty or losing confidence. You should treat the reworking of module(s) as part of the job.