Physical to Virtual (Cloud) Migration

This task will consist of a proposal for a major IT project. The proposal will identify a problem and propose an IT solution to the problem. Your proposal will also explain how you plan to implement your project to successfully resolve the problem, including a methodology for project development. Requirements: Discuss (suggested length of 15–20 pages) your project in a narrative proposal by doing the following: A. Proposal Overview (suggested length of 2–4 pages) : Create an IT proposal and project overview by doing the following: 1. Identify the problem. 2. Propose an IT solution. 3. Explain the plan to implement this proposed project. B. Review of Other Work (suggested length of 3–4 pages) : Provide a review of four other works that have been completed on your topic and that you will use as background for this proposed project. Note: These other works may include interviews, white papers, research studies, or other types of work by industry professionals. 1. Describe how each work reviewed relates to the proposed development of this project. C. Rationale (suggested length of 1–2 pages) : Provide a rationale showing the need for your proposed project. D. Current Project Environment (suggested length of 2–3 pages) : Provide a description of the current state of the project environment or the current state of affairs that makes your proposed project necessary. E. Methodology (suggested length of 1–2 pages) : Explain how you will apply a standard methodology (such as ADDIE or SDLC) for the implementation of your project. F. Project Goals, Objectives, and Deliverables (suggested length of 3–5 pages) : Explain the goals, objectives, and deliverables for the project, including the following information: 1. Provide a table showing the relationship between goals and their supporting objectives, including outcomes or deliverables. 2. Provide a description of project goals, objectives, and deliverables. G. Project Timeline with Milestones (suggested length of 1–2 pages) : Provide a projected timeline with milestones for your project, including the duration and start and end dates of each milestone. H. Outcome (suggested length of 1–2 pages) : Reflect on how you will measure the success and effectiveness of this project. I. Acknowledge sources, using in-text citations and references, for content that is quoted, paraphrased, or summarized. TASK 3. POST-IMPLEMENTATION REPORT: This task will consist of a post-implementation report for the project you proposed in task 2. Your report will explain how you implemented an IT solution to successfully resolve the identified problem, including your methodology for project implementation. Requirements: Develop a post-implementation report of your completed project in a narrative format by doing the following: A. Summary: Summarize the actual development of the completed project. B. Review of Other Work: Provide a review of three additional works on your topic (not referenced in task 2) that supported the actual development of this project. Note: These other works may include interviews, white papers, research studies, or other types of work by industry professionals. C. Changes to Project Environment: Describe the changes made to the project environment by the implementation of your project. D. Methodology: Explain how you applied a standard project management methodology for the implementation of your project. E. Project Goals and Objectives: Explain how some goals and objectives were met and why some goals and objectives for your project were not accomplished. F. Project Timeline: Explain why you did or did not meet the timeframes set for your project, including any differences between the projected dates and the actual completion dates. G. Unanticipated Requirements: Explain any unanticipated requirements or components and how you resolved them. H. Conclusion: Discuss actual results and potential effects of the completed project. I. Project Deliverables: Include artifacts showing evidence of project completion. Note: Possible deliverables may include the following: • code samples or screen shots • flowcharts, UML, or other process diagrams • charts, tables, and graphs • network diagrams (before and after) • training materials • technical IT product itself J. Acknowledge sources, using in-text citations and references, for content that is quoted, paraphrased, or summarized.