even before new requirements come up, some of the idiosyncrasies or edge cases would be overlooked in the new version and the project would take much longer tha

even before new requirements come up, some of the idiosyncrasies or edge cases would be overlooked in the new version and the project would take much longer than anticipated. if the current tech is so messed up to warrant a re-build, why would one expect that all the requirements are properly captured? having said that, stepping back and articulating the existing problems could be a viable first step. Identify and scope the problems before dreaming of solutions. /product engineer and party pooper hat off