Refactoring after development getting done rapidly?
Do you think that the refactoring process can be deferred while a thought that the quickness of development is the most crucial matter in business prevails? And if you answered YES to the question, are you sure that you never lose anything or less than another choice from your decision?
Considering that human brain has its limit, in the other words, memory is volatile. It can easily go away. And most projects are complex far enough to be lost in the mid. Then someone might say that using mnemonics like post-it would help to recollect the factors.
Now it's time to think about backlogs because it's strongly related to motivation. As the time goes by, the task becomes loose and slack. For example, suppose that you have a homework for class and you procrastinate it until a day before due date. Now you should do it but may feel troublesome for you lose your mind. That is the same as to the project. Deferred process would not be getting done clearly losing the motivation unless other incentives are given. It is a kind of waste!
Refactoring right after the development is truely important. Though it may take some time and seems wasteful, the project manager should cover the nuts and bolts.