The bulk of McConnell's Rapid Development System will endure regardless of future software technology. However, it is not the last word on development. There are many other Systems that contain useful methods and alternative approaches that can well be used in all or specific projects.
We can cherry pick from these Systems. For example:
Change made to the internal structure of software to make it easier to understand and cheaper to modify without changing its observable behavior.
Adam Cogan has a useful example to illustrate why refactoring is a worthwhile discipline:
What do you do when you see a directory structure like this:
* SSW/Images
* PDI/Images
* ABC/Image
a) Leave it, it is only a little inconsistency after all, and fixing it may cause some bad links and why fix something that isn't broken?
b) OR fix the inconsistency straightaway?
For me the only answer is b). Tackle these problems head on, in line with the fourth principle of eXtreme Programming - courage. Fix the problem now and save it from becoming a bigger problem later.
In short our Software Development System is open to best practice wherever it comes from. Whatever is needed to give the client the best software solution.