ABC Inc. specializes in migrating data to the cloud.

ANALYSIS:
ABC Inc. specializes in migrating data to the cloud. Recently, the company has been tasked to migrate data for a small airport to the cloud.
Project Topic -
XYZ Airport is a small airport in Naboo that has been operating for twenty years. This year, a number of hurricanes have passed through the area and as a result, some of the airport’s infrastructure, including its server rooms and IT equipment were damaged and deemed inoperable. With the rising costs of IT equipment, the airport has elected to not replace the damaged equipment and has been running its servers on minimal capacity. This has resulted in degraded services, impacting the day-to-day operations of the airport. The current management has decided to decommission most of its existing IT infrastructure and move everything into the cloud. They have hired ABC Inc. to provide cloud solutions to free the airport from the constraint of their old and costly IT infrastructure as well as reduce operational costs.
Goals & Objectives (Please feel free to add or remove from this section, this was used just to get the topic approved)

1. Audit the current data, including all the applications and services, to calculate how long and how much effort the data migration will require.
2. Inventory and decommission all damaged and unnecessary IT equipment
3. Inspect the data for quality and integrity as well as determine which ones must be transferred to the cloud
4. Create a migration plan in which all necessary support to properly migrate and deploy services and applications to the cloud are laid out
5. Provide a cost-effective cloud environment to host the all the airport’s data, applications, and services by implementing a pay-as-you go model
6. Migrate all the necessary applications, services, and data necessary for the airport’s daily operations into the cloud.
7. Establish post migration support including backup and disaster recovery procedures as well as provide training to existing IT personnel and end users

I. Proposal

A. Summary (suggested length of 2–4 pages): The Proposal Overview section introduces the problem and overviews the solution. It contains the "road map" for the organization of the remainder of the paper. Describe the problem the project addresses and then provide an overview of the project and the organization of the paper. Summarize the capstone’s highlights. Include the following in your summary:

1. Identify the problem: should include the context in which this problem exists. Summarize what will and will not be included in the project. Provide sufficient background information so that the reader can appreciate the need for a solution and the approach that will be taken in the project.
2. Propose an IT solution: Describe the proposed IT solution to the problem. Clearly identify the relationship between the problem and the proposed solution.
   Implementation Plan
3. Explain the plan to implement this proposed project: This section should contain the details of an implementation plan. Provide details on the different phases (if applicable). Explain how the project will be carried out and why it will be carried out in that manner. Discuss the plan for implementing the project.

B. Review of Other Work (suggested length of 3–4 pages): In this section review other works done by a third party that are relevant and directly relate to the project. Review at least four other works completed on the chosen topic. Summarize interviews, white papers, research studies, or other types of work by industry professionals. For example, if planning a server upgrade project, summarize articles that describe successful upgrade server solutions in other companies, comparisons of various server hardware and software products that are possible solutions, and any case studies that relate or are similar to the planned server upgrade. Include the following in your review:

1. Relation of Artifacts to Project Development: Provide a logical description of how each work reviewed relates to the proposed development of the project. Explain how each of the chosen works contextualize the problem or provide direction to the project.

Note: These other works may include interviews, white papers, research studies, or other types of work by industry professionals.

C. Rationale (suggested length of 1–2 pages): Summaries should include the rationale for choosing this project, including what makes this problem interesting or significant. The Project Rationale section provides a rationale for the project. It should address the reasons for implementing the project, as described in the Proposal Overview. The rationale may include and expand on both business and technical reasons to support the implementation. Justify the selection of the project.

D. Current Project Environment (suggested length of 2–3 pages) : This section describes and details the current project environment. It should also address specifically how the current state will set the direction for the definition and implementation of the proposed solution. Other details that support the description should also be included here as needed to support and succinctly define the project environment. Analyze the systems and describe the status of the project environment before the project began.

E. Methodology (suggested length of 1–2 pages) : This section describes and details the specific methodology. The methodology is the process that the project will follow when it is implemented. Include specific details to adequately describe the steps that will take place to fully execute the project. Explain how a standard methodology (such as PDCA, ADDIE, SDLC, Prototyping or Agile) will be applied for the implementation of the project.

F. Project Goals, Objectives, and Deliverables (suggested length of 3–5 pages): Provide a detailed explanation of the goals and objectives for the project, and explain what the project will provide. There should be a specific and clear identification of each goal and objective, as well as a clear and logical description with adequate detail of each of the goals and objectives. Address and explain the criteria that will be used to measure the objectives to demonstrate how each goal and objective will be measured. The project will include some sort of formal report. It will likely also include a technical IT product and/or a user’s manual or other documentation. Deliverables should provide a detailed logical explanation of what the project will provide to substantiate the work and completion of such. Include the following in the description:

1. Goals, Objectives, and Deliverables Table
   Goal Supporting objectives Deliverables enabling the project objectives
   1 Summarize project goal 1 1.a. Describe project objective 1.a. 1.a.i. Explain project deliverable 1.a.i
   1.a.ii. Explain project deliverable 1.a.ii
   …
   1.b. Describe project objective 1.b. 1.b.i. Explain project deliverable 1.b.i
   1.b.ii. Explain project deliverable 1.b.ii
   …
   … …
   …
   …
   2 Summarize project goal 2 2.a. Describe project objective 2.a. 2.a.i. Explain project deliverable 2.a.i
   2.a.ii. Explain project deliverable 2.a.ii
   …
   2.b. Describe project objective 2.b. 2.b.i. Explain project deliverable 2.b.i
   2.b.ii. Explain project deliverable 2.b.ii
   …
   … …
   …
   …
   … … …
   …
   …
   …
   …
   …
   …
   …
   … …
   …
   …
2. Goals, Objectives, and Deliverables Descriptions: Describe each of the project goals. Describe each objective. Explain how the objectives support the goals and explain how the objectives will be achieved. Explain what types of deliverables the project will provide and describe the key project deliverables expected by the end of the project. Provide a description of the project goals, objectives, and deliverables that aligns with the Goals, Objectives, and Deliverables Table.

G. Project Timeline with Milestones (suggested length of 1–2 pages): Provide a projected timeline with milestones for the project. These may be estimates that will most likely be adjusted, as many times the project will require adjustments during the development and implementation phases. Provide a projected timeline with milestones for the project, including the duration and start and end dates of each milestone. Include the following table:

Milestone or deliverable Duration
(hours or days) Projected start date Anticipated end date

H. Outcome (suggested length of 1–2 pages): In this section, describe the anticipated project outcomes and explain how the success of the project will be measured once completed. Explain the expected project outcomes and describe the evaluation framework to be used once the project is completed to assess the project’s success and effectiveness.
 

II. Post Implementation Report

A. Summary: The Summary section includes a logical overview of the project with sufficient detail to sufficiently describe the actual development of the entire project. Provide a precise description of the project. The description should also provide adequate detail to describe all the components of the project. The details should include a description of the flow of the project, including all the major aspects that were accomplished.

B. Review of Other Work: In this section, provide an expanded review of the Review of Other Work section in part I, including three additional third-party artifacts on the topic that supported the development of the project, and explain how the artifacts supported the implementation.

Note: These other works may include interviews, white papers, research studies, or other types of work by industry professionals.

C. Changes to Project Environment: This section describes and details changes to the project environment made by the implementation of the project, after its completion. Analyze the systems and describe the status of the project environment after the implementation of the project.

D. Methodology: This section describes and details the specific methodology. The methodology is the process that the project filled by being implemented. Explain how a standard methodology was applied for the implementation of the project.

E. Project Goals and Objectives: In this section, provide a detailed explanation on how some goals and objectives were met and why some goals and objectives for the project were not accomplished. Identify the objectives that were met and explain how they were met, and then explain the reasons why some objectives were not accomplished.

F. Project Timeline: In this section, compare the projected and actual timelines of the milestones or deliverables of the project and explain why the differences occurred. Explain the reasons for each deviation of the actual time frame from the estimated time frame.
Note: All timeline dates MUST be in the past as this document is an after-action report that should reflect a project that is completed.

Note: Since this task represents an "After-Action Report" - please ensure that all timeline dates are in the past so as to reflect a project that has been completed.

G. Unanticipated Requirements: In this section, describe the requirements or components that were not anticipated at project initiation but emerged during implementation. Describe the problems encountered and the unanticipated requirements, and then explain how they were resolved or why they were not solved.

H. Conclusion: In this section, provide an explanation of the actual results and potential effects of the completed project. Describe the actual project accomplishments and discuss the immediately observable effects and potential future impacts of the completed project on the project environment. Explain why the project is or is not considered successful using the evaluation framework from the Outcome section in the project proposal.

I. Project Deliverables: In the Project Deliverables section, explain and detail the project key deliverables. The actual project development will be documented by the key deliverables. The project includes some sort of formal report. The deliverables should provide a detailed logical explanation of what the project provided to substantiate the work and completion of such. Describe the artifacts being used to show evidence of the project’s completion and use the appendices to include the actual artifacts. Actual project artifacts may include code samples or screen shots; flowcharts, UML, or other process diagrams; charts, tables, and graphs; network diagrams (before and after); training materials; and/or the technical IT product itself.

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

Sample Solution