Scribd
Upload
42 views2 pages

Re-Migration Blueprint: A Small Stout-Bodied Short-Eared Tailless)

1. The document outlines a re-migration blueprint providing steps to cleanse data, create a schedule, and establish decision-making bodies. 2. It recommends using a small pilot, creating a reusable blueprint, and delivering value through subprojects while expecting overruns. 3. The scope of re-migration involves moving data between different product versions with proper training, vetting, and extended post-live support.

Uploaded by

Anonymous ZGcs7MwsL
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
42 views2 pages

Re-Migration Blueprint: A Small Stout-Bodied Short-Eared Tailless)

1. The document outlines a re-migration blueprint providing steps to cleanse data, create a schedule, and establish decision-making bodies. 2. It recommends using a small pilot, creating a reusable blueprint, and delivering value through subprojects while expecting overruns. 3. The scope of re-migration involves moving data between different product versions with proper training, vetting, and extended post-live support.

Uploaded by

Anonymous ZGcs7MwsL
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Re-migration Blueprint

Need

1. Cleanse data before the Re-migration.

2. Set a schedule and stick to it.

3. Create a high-level decision-making body to arbitrate between different points of view, such
as lines of business or operations and IT.

4. Use a guinea pig (a small stout-bodied short-eared tailless)

5. Create a reusable blueprint.

6. Don't try to do everything at once.

7. Create small subprojects that can deliver value along the road.

8. Expect time and cost overruns

9. Try to enable and retain existing IT employees, even if you're changing IT platforms.

10. Have end users practice using the new system before official rollout.

11. Manage the migration strictly

12. Be prepared to quickly fix glitches in the new system.

Scope of Re-migration

1. Table to Table Re-Migration


2. Product to Product Re-migration (consider all functions)
3. Take data from R10 to R16 best fit
MBL need create Proposal as detailed product with function.
-Without Requirement Gathering no need Pre-assessment.
-Need Proper training before Re-migration on R16
-Steps B best
-Steps A Well
-Steps C Fair
-Need decision to Re-migrate Version
-Clarify Techmill quality
-Clarify past working experience
-Need third party Development Vetting from Temenos before handover project.
-Extend post-live support

IB
Need Two factor security with IB

You might also like