A Fortune 1,000 company with deep pockets is likely to be sued even if its systems are working properly. Thus, unless some extraordinary federal legislation freezes such year 2000 litigation, assume you'll be facing a lawsuit. They will do this by reminding us of the very same things that good project managers and software engineers have been recommending for decades. Develop a formal, disciplined methodology for your year 2000 project, and keep an audit trail to demonstrate that your people are following it meticulously. Testing is important, and make sure you carry out baseline testing and regression testing.
Configuration management is critical, too.
The largest companies in the land are realizing that their potential legal exposure to year 2000 is hundreds of millions, if not billions, of dollars. If that's the case, you should consider going a step beyond showing the best practice material to your lawyers. Chances are it will be one of the most terrifying and humbling experiences you've ever had in your professional career. This may seem like an exaggeration. But remember that in most software lawsuits, the jurors are uninformed computer illiterates who have a difficult time maintaining any interest in the abstract issues associated with software.