The crucial issue is that a Business Analysis for the implications of Euro must be done. And I do not see anything happening in South Africa to assess those Business Requirements. And this is now on the critical path, with a very short leadtime.
0. These problems MUST be taken seriously. Act today.
1. Y2k requires a total change to software (and possibly) hardware. Euro is a business and software problem. You might share coding resource, but presumably analysis and design would be done by separate teams.
2. Fix your environment as your first priority. Make sure that your replacement Operating System and utilities software is installed as soon as possible. Acquire or hire a small CMOS machine with the latest software to act as a "time machine". This is critical for bridging the gap from "old" to "new" software. Alternatively use an LPAR type approach with non-shared DASD. If this is not done, neither project will work.
3. On a parallel path, start two projects, one for Y2k and one for Euro. But start both now.
4. Ensure that your steering committee controls both projects.
5. Euro is a fixed target for 1999-01-01. You have less than 10 months. You must plan at least one month for testing.
6. Target Y2k conversion for Dec 31 1998 to allow a yearend test.
The essence is that both projects have the same schedule date. Time is very short. It is crucial to have at least started on the Inventory side of Y2k within two months. Keep this phase short. I have heard people talking about 3 months for Inventory. We cannot spare that time. Maximum One Month.
I would warn against "short-cuts" in Y2k. As a Wise Man said, "Short-term solutions fail in the long term". B>)