Project Management Plan of a New Restaurant This project management plan is majorly concerned primarily with the first two steps which are defining the project; the project objective is broken down into a series of manageable steps called tasks and designing the project process; this work is performed by the project manager and is presented in the GANTT chart where the tasks are displayed in more detail (Hamilton, 2004). Besides, for this project, the stakeholders will actually deliver the project. The final step of developing the project management process is a continual reappraisal of the way in which tasks are planned for and implemented; this is an ongoing process that begins once the first task is underway.

Assumptions

In this project management plan, there are certain choices that had to be made regarding the parameters to which this project subject. These include the assumption that the general working hours are; weekdays from 8am till 12pm and 1pm till 5pm while weekends are free days to the workers. The calculations are based on an 8-hour day and 40-hour week and the only exception to this is the first day of the project, which is Saturday 2 February 2013 (Lock, 2007). In addition, each worker will only work up to a maximum of 8 hours per day and the activity durations are presumed to be correct, although extra flexibility has been built into the plan to mitigate any time problems. Finally, the resource costs are known and have been calculated in the project costing table, however, the fixed costs are not known and so have been estimated; any slight changes in the fixed costs will affect the total project cost.

Project Objectives

This project management plan aims at creating a fully operational 5-star restaurant as part of George Wright's business that will be prepared to receive guests for a Grand Opening day.

Tasks

In order to achieve the project's objectives the following tasks must be achieved. The tasks have been grouped into the following summary tasks; building work, interior design, new staff, food, preparation for grand opening.

Action Plan

The Critical Path Method (CPM) is a way of creating a logical sequence of the work tasks and activities that are described above. The Gantt chart highlighted in the paper clearly presents the tasks necessary to complete the project showing how the tasks are linked to and flow from each other.

Definition

The following are definitions of terms, abbreviations and acronyms used in this document.

Term

Definition

CIO

Chief Information Officer

DoIT

Division of Information Technology

Project Plan Overview and Critical Assumptions

The purpose of the project plan is to present the detail required to successfully execute and control the project, facilitate communication among project stakeholders, and document approved schedule baselines. The project plan is a living document and is expected to change over time as more information about the project becomes available. In this regard, this project plan is developed based upon certain key assumptions as noted in the Project Charter (Ireland, 2006). Any changes to these assumptions may impact the project schedule, projected costs, the project scope and the project quality. The assumptions used in this project plan are thus highlighted below as;

The goals of this project support the vision, mission, and goals of DoIT, helping faculty, staff and students realize their visions through the use of information technology.

The project helps DoIT achieve its goal of outstanding customer service.

DoIT management actively supports improvements in each of the seven component areas: framework, tools, project management skills, thinking, culture, politics, and communication.

DoIT management and staff comply with specifications for all project management responsibilities as stated in the "Project Management at DoIT -- A Social Contract" document.

The timeline is reasonable and doable. The phased rollout supports early success and continued improvement. The project includes a lengthy implementation as components are developed and implemented, followed by sustained competency and improvements in the seven component areas.

DoIT management assigns key project roles and adequate budget for the development and implementation of this project.

Effective, adequate, and appropriate levels of communication occur between DoIT management, the sponsor, and the project team during all phases of the project.

The framework deliverable avoids excessive detail to ensure common understanding, flexibility, and adoption.

The deliverables of the project are implemented DoIT-wide, supporting many diverse functional groups, projects, and customers.

Project Work Plans

Work Breakdown Structure

The work breakdown structure identifies the project's tasks to provide a framework for organizing and managing the work of the project.

Project Management Initiative

Phase I

Initiate Project

Develop Project Charter

Plan Project

Develop Work Plan

Develop Project Control Plan

Finalize Project Plan and Gain Approvals

Develop Work Breakdown Structure

Develop Project Staffing Plan

Develop

Project Schedule

Develop

Project

Budget

Develop Quality Management Plan

Define Scope

Define Requirements

Define High-Level Roles

Define High-Level Budget

Identify High-Level Control

Strategies

Finalize Charter

Develop Communication Plan

Execute and Control Project

Design Content formats

Build the Framework

Test the Framework

Implement the Framework

Close the Project

Design the Framework

Define stages and activities

Design

web Delivery Tool

Write the content

Review content for quality

Build web tool prototype

Test web tool usability

Test content usability

Adjust tool and content based on feedback

Move web tool to production environment

Announce

Tool

availability

Conduct post project review

Celebrate

Staffing Plan

The purpose of the staffing plan is to make certain the project has sufficient staff with the right skills and experience to ensure a successful project completion.

Role Requirements

The following is a detailed breakdown of the roles required to execute the project. The requirements include the project role, the project responsibility of the role, skills required, number of staff required in completing the roles, the estimated start date and the expected duration the staff resource will be needed on the project.

Project Team

Project Manager

Lead team, report status

Project Management

1

7/2/13

6 months

Core Team

Review deliverables, assure quality

Project Management

4

9/2/13

4 months

Content Developer

Create framework content

Research and web writing skills

1

9/2/13

4 months

Web Designer

Design web-based performance mgmt. tool

Web design, web writing skills

1

10/2/13

3 months

Web Developer

Build the web-based performance management tool

Web development

1

11/2/13

2 months

Review Team

Evaluate deliverables, promote use

Project Management experience

20

11/2/13

2 months

Staff Assigned to Roles

The following is a detailed breakdown of the actual staff assigned to the project role, the amount of Full Time Equivalent (FTE) requested for the role, the actual FTE acquired and the labor rate as well as the unit of the labor rate for the resource and the source from which the resource is recruited.

Project Team

Project Manager

Name1 - Project Manager

1.00

1.00

$85

hour

DoIT - Systems Engineering Operations

Core Team

Name4

.10

.10

$70

hour

DoIT- Network Services

Name5

.10

.10

$70

hour

DoIT -- Enterprise Internet Services

Name6

.10

.10

$70

hour

DoIT -- Data Resource Management Technologies

Content Developer

Name6

.90

.90

$70

hour

DoIT -- Data Resource Management Technologies

Web Designer

Name7

.05

.05

$75

hour

Academic Technology Solutions

Web Developer

(Tbd.)

.05

.00

$65

hour

Academic Technology Solutions

Review Team

(20 reviewers)

Various Project Managers

.10

.10

$70

hour

See Appendix A for detail list

Total

2.40

2.35

Staff Resource Loading Chart