Future Technology Data Center Relocation: Project Charter & Statement of Work

Scenario
Charles Parker, network administrator at Future Technology (FT),  has been given the responsibility of relocating the large data center to  a new office building. Careful planning is needed because FT operates  in the highly competitive cellular industry. FT is one of four national  software companies that provide an accounting and business management  package for cellular service locations and sales distributors. A few  years ago, FT jumped into the “application service provider” world.  Their large data center provides clients with remote access to FT’s  complete suite of application software systems. Traditionally, one of  FT’s primary competitive advantages has been the company’s trademark IT  reliability. Due to the complexity of this project, Charles will have to  use a parallel method of implementation. Although this will increase  project costs, a parallel approach is essential if reliability is not to  be compromised.
Currently, FT’s data center is located on  the fourth floor of a renovated old school building in downtown Mobile,  Alabama. The company is moving to a new, one-level building located in  the recently developed industrial complex at Mobile International  Airport. On April 15, Charles is formally assigned the task by the Vice  President of Operations, Marion Hassing, with the following guidelines:
·        From start to finish, it is anticipated the entire project will take three to four months to complete.
·        It is essential that FT’s 315 clients suffer no downtime.
Hassing advises Charles to come back to the Executive Committee  on May 1, with a presentation on the scope of the project that includes  costs, “first-cut” timeline, and proposed project team members.
Charles had some preliminary discussions with some of FT’s  subject matter experts, managers, and directors from each of the  functional departments and then arranged for a full-day scope meeting on  April 19 with a few of the managers and technical representatives from  operations, systems, facilities, and applications. The scope team  determined the following:
·        Four to five months is a  feasible project timeline and first-cut cost estimate is  $90,000-$100,000 (this includes the infrastructure upgrade of the new  site).
·        Critical to the “no-downtime” requirement is  the need to completely rely on FT’s remote disaster recovery “hot” site  for full functionality.
·        Charles will serve as  project manager of a team consisting of one team member each from  facilities, operations/systems, operations/telecommunications, systems  & applications, and customer service.
Develop a Project Charter and a  Statement of Work for the Future Technology Data Center  relocation project.  These documents will be submitted to Marion  Hassing for acceptance.

Struggling with where to start this assignment? Follow this guide to tackle your assignment easily!

Developing a comprehensive Project Charter and Statement of Work (SOW) is crucial for the successful relocation of Future Technology’s (FT) data center. Below is a structured guide to assist you in crafting these documents effectively.

1. Understanding the Project Charter

The Project Charter is a formal document that authorizes the project, outlining its objectives, scope, stakeholders, and overall framework. It serves as a reference point throughout the project’s lifecycle.

Key Components of a Project Charter:

  • Project Title: A concise name for the project.
  • Purpose or Justification: A brief statement explaining why the project is being undertaken.
  • Objectives: Specific, measurable goals the project aims to achieve.
  • Scope: A high-level description of the project’s deliverables and boundaries.
  • Stakeholders: List of key individuals or groups involved, including the project sponsor and team members.
  • High-Level Requirements: Essential features or functions that the project must include.
  • Assumptions and Constraints: Factors considered true without proof and limitations that could impact the project.
  • High-Level Timeline: An overview of major milestones and the projected schedule.
  • Budget Estimate: Preliminary financial resources allocated for the project.
  • Approval Signatures: Endorsements from project sponsors or key stakeholders.

Steps to Create the Project Charter:

  1. Initiate with a Project Overview:

    • Define the project’s purpose, such as relocating FT’s data center to enhance infrastructure and maintain IT reliability.
  2. Detail the Objectives:

    • Ensure zero downtime for FT’s 315 clients during the transition.
    • Complete the relocation within a four to five-month timeframe.
    • Adhere to the budget estimate of $90,000-$100,000.
  3. Define the Scope:

    • Outline tasks like setting up the new data center, migrating systems, and decommissioning the old facility.
  4. Identify Stakeholders:

    • List individuals such as Marion Hassing (Vice President of Operations), Charles Parker (Project Manager), and team members from various departments.
  5. Specify High-Level Requirements:

    • Utilize FT’s remote disaster recovery “hot” site to ensure full functionality during the move.
  6. List Assumptions and Constraints:

    • Assume availability of necessary resources and highlight constraints like the strict no-downtime requirement.
  7. Outline the High-Level Timeline:

    • Start: April 15
    • Scope Meeting: April 19
    • Presentation to Executive Committee: May 1
    • Project Completion: August 15 (latest)
  8. Provide a Budget Estimate:

    • Allocate funds for infrastructure upgrades, equipment, and contingency plans within the $90,000-$100,000 range.
  9. Secure Approval Signatures:

    • Obtain endorsements from Marion Hassing and other key stakeholders.

2. Crafting the Statement of Work (SOW)

The SOW is a detailed document that outlines the project’s work requirements, deliverables, and timelines. It serves as a roadmap for project execution.

Key Components of a Statement of Work:

  • Introduction: Brief overview of the project.
  • Purpose: The rationale behind the project.
  • Scope of Work: Detailed description of tasks and deliverables.
  • Location of Work: Where the project activities will occur.
  • Period of Performance: Project start and end dates.
  • Deliverables Schedule: Timeline for each deliverable.
  • Applicable Standards: Standards or guidelines to follow.
  • Acceptance Criteria: Conditions for deliverable acceptance.
  • Special Requirements: Any specific needs, such as special skills or equipment.

Steps to Develop the SOW:

  1. Introduction:

    • State that the document outlines the SOW for relocating FT’s data center to a new facility at Mobile International Airport.
  2. Purpose:

    • Emphasize the goal to maintain FT’s IT reliability and ensure no downtime for clients during the relocation.
  3. Scope of Work:

    • Detail tasks such as:
      • Assessing current data center infrastructure.
      • Planning the migration strategy.
      • Setting up the new data center.
      • Testing systems at the new location.
      • Migrating data and applications.
      • Decommissioning the old data center.
  4. Location of Work:

    • Specify both the current and new data center locations.
  5. Period of Performance:

    • From April 15 to August 15.
  6. Deliverables Schedule:

    • Provide a timeline with milestones, e.g., completion of infrastructure setup by June 15.
  7. Applicable Standards:

    • Adhere to industry best practices for data center migration and FT’s internal IT standards.
  8. Acceptance Criteria:

    • Define criteria such as successful system tests and zero client downtime during migration.
  9. Special Requirements:

    • Note any needs for specialized equipment or expertise, like advanced

Place this order or similar order and get an amazing discount. USE Discount code “GET20” for 20% discount