Produce a project plan which documents:
Migration strategy—Which method is most appropriate for your site.
Fallback—What to do in case the migration fails. The plan you evolve will be site-specific, but some general issues are discussed in Chapter 7, “Test: Ensuring Stability and Performance”.
Application test suite—What validation and performance testing to perform for acceptance. See Chapter 6, “Implement: Making Database Administration Changes” for guidance.
Bridging—Ways to minimize the impact to users during the migration. Refer to the business requirements you gathered in Chapter 3, “Analyze: Documenting Your Environment”.
Environment—Additional resources and changes to the environment needed based on the information you gathered in Chapter 3, “Analyze: Documenting Your Environment”.
Scheduling—How much time the migration will take based on the level of complexity and business needs. Refer to the business requirements you gathered in Chapter 3, “Analyze: Documenting Your Environment”.
Producing the following documentation may also be useful:
A work breakdown that lists tasks chronologically and assigns them to specific roles like the one in Appendix B, “Sample Migration Task Lists”.
Specification for application changes. The details of needed application changes are discussed in Chapter 5, “Implement: Making Required Application Changes”.
