IWCE – 2009 MIGRATING LEGACY SYSTEMS

1. IWCE – 2009MIGRATING LEGACY SYSTEMS MIGRATING LEGACY SYSTEMS

2. DEVELOP THE BIG PICTURE VIEW • WHERE ARE WE TODAY • WHERE DO WE WANT TO BE • WHY DO WE WANT TO BE THERE • HOW ARE WE GOING TO GET THERE • WHAT ARE THE RISKS WE WILL FACE • DEFINE THE TEAM AND UNDERSTAND THEIR ROLE • AVOID THE KEY MISTAKES • CLOSE OUT MIGRATING LEGACY SYSTEMS

3. WHERE ARE WE TODAY • Define the system you want to migrate from • Are you sure you know the full scope • What does it do for you now • What does it not do that you need done • Who does it serve • When was it implemented and at what cost • Was there a planned lifecycle for the system and are you there • Both yours and the vendors • Where is the technology going/gone • What is driving the need • Technology Advancement, Regulatory issues, Obsolescence MIGRATING LEGACY SYSTEMS

4. WHERE DO WE WANT TO BE • Define the end product system capability • What do you want the new system to be able to do (Day 1) • Will the new system be dynamic or static • Is the new system scalable and to what degree • Consider Firmware and Software viability MIGRATING LEGACY SYSTEMS

5. WHY DO WE WANT TO BE THERE • Develop a clear set of reasons why this project needs to be done • You are going to have to convince someone to pay for new system • Is it a regulatory requirement • If it is a mandate; • Is it funded, partially funded or unfunded • Will it improve our service capabilities • Will it reduce O&M • What is the expected ROI (Service Life or $$) MIGRATING LEGACY SYSTEMS

6. HOW ARE WE GOING TO GET THERE • It’s best not to squat when you are wearing spurs • Planning and Coordination are the keys to successful project implementation • Define what has to be done in each step • Know who will be affected during that step • Bring the key players together • Talk through each step and look for unintended consequences • Have a “Step Back” plan, an “Alternative Service” plan, and a “Contingency Plan” • Murphy lives in your town and works for your organization MIGRATING LEGACY SYSTEMS

7. WHAT ARE THE RISKS WE WILL FACE • Risk is inherent in any project • The more critical the system being replaced is to the organization the higher the risk • Minimizing risk is a process, it is not luck • Define the things that can go wrong and plan around them • Don’t forget the back up plan can go wrong too MIGRATING LEGACY SYSTEMS

8. DEFINE THE TEAM AND UNDERSTAND THEIR ROLE • Who authorizes the expense • Who is the project Champion • Who is the project Owner • Who is the project Manager • Who are the project participants • Who are the project Beneficiaries • Who will be affected by the project • Who is the project Partner MIGRATING LEGACY SYSTEMS

9. AVOID THE KEY MISTAKES • Identify those people who have done similar projects and seek their counsel • Include your Partner as chances are they have done this before and they too need it to be successful • What worked really well • What did not work well • What would they do “the next time” • Where were the surprises MIGRATING LEGACY SYSTEMS

10. CLOSE OUT • Hot Wash, Cold Wash, After Action Review, whatever you want to call it, HAVE ONE • Focus on the facts and leave the blame, finger pointing and emotions out of it • Encapsulate the Lessons Learned • Identify the benefits • Communicate! Provide a summary report to everyone involved • And what are you going to do with the old stuff MIGRATING LEGACY SYSTEMS