DRAFT

PROJECT CHARTER/PLAN
FOR

SMALL PROJECTS

This document outline is based on the IEEE Standard 1058.1-1987 for Project Management Plans. This is the controlling document for managing a Production Services project, and it defines the technical and managerial processes necessary to deliver the project requirements. The paragraphs written in the Comment style are for the benefit of the person writing the document and should be removed before the document is finalized.

PROJECT NAME:

TAJ HOTEL MANAGEMENT SYSTEM

PROJECT NUMBER:

RFP 123456

VERSION: 1.0
[24-11-2011]

M L ADITYA

11/24/11

DRAFT REVISION CHART

This chart contains a history of this documents revisions. The entries below are provided solely for purposes of illustration. Entries should be deleted until the revision they refer to has actually been created. The document itself should be stored in revision control, and a brief description of each version should be entered in the revision control system. That brief description can be repeated in this section. Revisions do not need to be described elsewhere in the document except inasmuch as they explain the development plan itself.
Version Primary Author(s) Description of Version Date Completed

Draft Preliminary Final Revision 1

TBD TBD TBD TBD

Initial draft created for distribution and review comments Second draft incorporating initial review comments, distributed for final review First complete draft, which is placed under change control Revised draft, revised according to the change control process and maintained under change control Revised draft, revised according to the change control process and maintained under change control TBD

TBD TBD TBD TBD

Revision 2

TBD

TBD

etc.

TBD

TBD

76699349.doc 23/11/2011 11:02:00

Page 2

DRAFT CONTENTS
New paragraphs formatted as Heading 1, Heading 2, and Heading 3 will be added to the table automatically. To update this table of contents in Microsoft Word, put the cursor anywhere in the table and press F9. If you want the table to be easy to maintain, do not change it manually.

REVISION CHART....................................................................................................................2 CONTENTS..............................................................................................................................3 1. INTRODUCTION ...................................................................................................................5 PROJECT BACKGROUND AND RATIONALE.....................................................................................5 RESPONSIBILITY........................................................................................................................5 SCOPE.....................................................................................................................................5 1.4 PROJECT OBJECTIVES..........................................................................................................5 1.5 PROJECT DELIVERABLES......................................................................................................7 1.6 MILESTONES......................................................................................................................7 BUSINESS CASE........................................................................................................................7 PROJECT ORGANIZATION.........................................................................................................8 ORGANIZATIONAL STRUCTURE....................................................................................................8 2.2 PROJECT RESPONSIBILITIES...................................................................................................9 MANAGERIAL PROCESS..........................................................................................................10 ASSUMPTIONS, DEPENDENCIES, AND CONSTRAINTS......................................................................10 3.2 RISK MANAGEMENT........................................................................................................10 MONITORING AND CONTROLLING MECHANISMS..........................................................................10 QUALITY PLAN .....................................................................................................................10 CHANGE CONTROL PLAN ........................................................................................................11 3.6 STAFFING PLAN...............................................................................................................11 4. TECHNICAL PROCESS.........................................................................................................12 4.1 SYSTEM DOCUMENTATION.................................................................................................12 4.2 PROJECT SUPPORT FUNCTIONS............................................................................................12 5. WORK BREAKDOWN STRUCTURE, SCHEDULE, AND BUDGET..................................................13 5.1 WORK BREAKDOWN STRUCTURE........................................................................................13 5.2 BUDGET..........................................................................................................................14 5.3 SCHEDULE.......................................................................................................................14 6. ADDITIONAL COMPONENTS.................................................................................................15

76699349.doc 23/11/2011 11:02:00

Page 3

DRAFT
7. APPENDICES......................................................................................................................16

76699349.doc 23/11/2011 11:02:00

Page 4

DRAFT 1. INTRODUCTION
The project proposed is the Hotel Management system for TAJ HOTEL, Visakhapatnam. The purpose of the project is manage the Taj Hotel in which it includes the manging of the rooms, restaurant and nominal audit of the hotel . the nominal audit include the general management operations and services provide by the hotel to all the customers and also the monitoring the functions of hotels. The end users of this project (HMS) are the hotel staff, cooking people (chefs), Hotel Mangers etc. The project designed in such a way that it serves or helps the end-users from the reception to the room service, restaurant billing and services. So that customer can have a better communication regarding the room availability, extension of the room, and also the billing in restaurant and room will be accurate.

Project Background and Rationale

The taj Hotel is the one of the familiar hotel in the region, which provides all the facilities like the star hotel serves to the customers, but it is lagging of the good management system in the room services, restaurant and general audit services and automated tasking systems. So as to recover these issues the Taj Mangers decided to design a managing system that works for the hotel which gives a good recognistion and also it increases the revenue through this system. And also the people of the Taj

Responsibility
Executive Sponsor: Project Sponsor: Project Manager: Acceptors:

Enter name and title here Enter name and title here Enter name and title here Enter name and title here Enter name and title here Enter name and title here Enter name and title here Enter name and title here Enter name and title here

Reviewers:

Enter name here Enter name here Enter name here Enter name here Enter name here Enter name here Enter name here Enter name here Enter name here

Scope
Identify project boundaries, whats included, and what is not covered by this project..

1.4 Project Objectives

What specific problem is this project trying to solve and what would constitute an acceptable solution?

76699349.doc 23/11/2011 11:02:00

Page 5

DRAFT
How will the infrastructure be different once the project is successfully completed?

76699349.doc 23/11/2011 11:02:00

Page 6

DRAFT

1.5 Project Deliverables

List all of the major items to be delivered, delivery dates, delivery locations, delivery method and quantities necessary to satisfy the projects requirements.

1.6 Milestones
List those significant points that will occur during the execution of the project that can be used to assess its progress.

Business Case
State whether a business case has been prepared or not and if one has been developed provide a reference to the document. Indicate whether the business case was approved. Is this project to be gated or not? If so, what is the composition of the gating committee.

76699349.doc 23/11/2011 11:02:00

Page 7

DRAFT PROJECT ORGANIZATION

Organizational Structure
Describe the internal management structure of the project. Use an organization chart to describe the lines of authority and communication within the project. A sample follows.

y p e y p e

a m t it le

e h

h e r e r e e h h e r e r e

y p e y p e

a m T ey p h e e rn e a m T ey p h e e rn e a m t i t l e T h y e p r e e t i t l e T h y e p r ee t i t l e

76699349.doc 23/11/2011 11:02:00

Page 8

DRAFT

2.2 Project Responsibilities

Use a RASCI chart to identify who is responsible for what within the scope of this project. For each activity required by the project, identify who is responsible for doing the work (R); who is accountable for getting the work done (A); who must be consulted prior to completing the work (C); who must provide support in the creation and delivery of the work products (S); and who needs to be informed after the fact (I). These people are the projects stakeholders. An example follows.
Roles and Responsibilities Definition M atrix Exam ple Project Participants Project Project Account Business SE SE Team Technical M anager Relations Supervisor Manager Member Lead Specialist A S S S S S S S S S S S S S S S A I A S S C S C A S S S S S S C S R S S

Activities

Project Project Manager Team Leader R A R R R R A R R R R S R R S S S R R S S

Establish project Start-Up team Create Project W orkbook Develop Start-Up project plan Establish customer relationship Outline project scope Set up project management environment Establish change m anagem ent process Determine financial procedures Identify project risk Announce project Review project Start-Up

C S R S

Key R = Responsible for the process A = Approves/accepts the deliverables from the process S = Supports steps in the production of the deliverables I = Information needed about the status and content of the deliverables C = Consult for inputs, information, and/or contributory deliverables * For each role you choose to use on your project, you should include a narrative role definition on an attachment.

76699349.doc 23/11/2011 11:02:00

Page 9

DRAFT MANAGERIAL PROCESS

Assumptions, Dependencies, and Constraints
Describe the assumptions upon which the project plans are based, the dependencies of the project plans, and the constraints upon the project plans (e.g., schedule, budget, quality, functionality, etc.) An assumption is something that can effect the project but you cannot control.

3.2 Risk Management

Describe any serious risks that might affect the project and how you plan to deal with them.

Monitoring and Controlling Mechanisms

Describe how project cost, schedule, quality, and functionality will be tracked throughout the project. How often will the reviews take place, with whom? A sample progress report is provided.

Quality Plan
A sample plan is provided.

76699349.doc 23/11/2011 11:02:00

Page 10

DRAFT

Change Control Plan

A simple change control process must be established. A sample is available. A simple change log should be kept; a template is provided.

Project Number: Change Requested No. by:

Description

Action IDR

Tar Date Completed/Comments get Date

I Implement D Defer R - Reject

3.6 Staffing Plan

Describe the numbers and types of personnel needed to conduct the project. Describe the required skill levels, start times and duration on the project

76699349.doc 23/11/2011 11:02:00

Page 11

DRAFT 4. TECHNICAL PROCESS

4.1 System Documentation
List the documents that will be developed for the project, including milestones, reviews, and signoffs for each document. Two kinds of documentation are necessary; those that are outputs of the delivery process, and those that are fundamental to the project management process. Some of these documents may not be relevant for every project The documentation list from the delivery process might include (this is not an exhaustive list): Sys tem Requirements Specification System Design Test Plan Installation Plan Transition/Cut over Plan Service Level Agreement Operations Manual User Manual Project Charter/Plan (this has many embedded documents) Project Status and Tracking Report

The project management process has only two principal documents:

4.2 Project Support Functions

If the project requires supporting processes such as configuration management, problem management, Help Desk support, etc, identify who is responsible for providing the function.

76699349.doc 23/11/2011 11:02:00

Page 12

DRAFT 5. WORK BREAKDOWN STRUCTURE, SCHEDULE, AND BUDGET

5.1 Work Breakdown Structure
The work breakdown structure (WBS) is a method of representing, in a hierarchical manner, the component parts of a process or product. A product WBS partitions a large entity into its components. Each component and its interfaces are identified, resulting in a clearer identification of the larger system. The project should be de-composed into at least three levels of detail with the lowest level being the tasks to be assigned to individual contributors. A short article describing the process is available. A sample template follows.

Task Specification Template

Specification

Data Category Activity Number: Activity Name: Activity Description:

Estimated Duration: Resources Needed: Personnel: Skill: Tools: Travel: Work Products (ie. Deliverables) Predecessors: Successors: Completion Criteria: Risks: Implementation: Personnel assignment Starting Date Completion Date: Costs Budgeted: Costs Actual: Comments

76699349.doc 23/11/2011 11:02:00

Page 13

DRAFT

5.2 Budget
Describe the projects budget allocated to capital, staffing costs, and consulting
As of mm-dd-yy Capital Costs Actual Budget Task 1 Task 2 Task 3 . . . . . . Task n Manpower Actual Expected Remainder 0 0 0 0 0 0 0 0 0 0 0

To Date Committe Expected Remainde Budget To d r Date 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

5.3 Schedule
Describe the schedule for the various project functions, activities, and tasks, taking into account the various dependencies and required milestone dates and deliverable dates. You can express schedules either as absolute calendar dates or as times relative to key project milestones (e.g., requirements signed off + 60 days).

76699349.doc 23/11/2011 11:02:00

Page 14

DRAFT 6. ADDITIONAL COMPONENTS

Include additional components needed to manage your specific project. Possibilities include subcontractor management plans, security plans, training plans, hardware/software procurement plans, facilities plans, installation plans, and maintenance plans.

76699349.doc 23/11/2011 11:02:00

Page 15

DRAFT 7. APPENDICES
Include supporting detail that would be too distracting to include in the main body of the document.

76699349.doc 23/11/2011 11:02:00

Page 16