Resource Management Plan

Tech-Way Omni

Development Tool Management System (DTMS) Communications Plan

Page 1 of 2

A. General Information

Prepared by:

Student Name

Date: 29 November 2004

Authorized by: Student Name

Project Description (Summary) Remote access services that provide network connectivity and security to

company resources.

B. Stakeholder List All Stakeholders are located in the same geographical locations

Stakeholder Name / Title Project Role

Architecture Support Group The customer who will use the software to support the development teams.

They are the final signoffs for the requirements and delivery of the software.

Ed Mann – Architecture Group

Manager

Customer Lead and interface point. He will receive copies of the weekly status

report. He will be responsible on the sign-off and acceptance milestones.

Mike Spam – Assistant Vice President

Web Architecture and Project Manager

Executive Management. Mike will manage the entire project from Scope to

acceptance and final launch. Mike will be responsible for allocation of all resources and approval of time schedules for the entire project.

Development Team Focus Group Responsible for providing reviews of requirements, technology direction, and

beta reviews. The group will receive weekly status reports, access to all documentation for the project, and access to of issues tracking database.

C. Communication

Document Description

Audience Expected Action Comm. Class.

Input Method Output Method Frequency Responsible resource

Project Status Report

All project team members.

Individual Status submitted every Friday

Mandatory Status Update Form

Combined Status e- mailed every

Monday

Weekly per the expected

action.

Tony

Project Status

Web

AVP’s from each

organization

Update project

status, escalation

Mandatory Web input Update

reminder sent

Monthly Tony

Tech-Way Omni

Development Tool Management System (DTMS) Communications Plan

Page 2 of 2

of all risk issues through e-mail

Project Status

Meeting

All project team

members.

Interaction Mandatory In person Meeting Notes

in Word format

Weekly per

the expected

action.

Bob

Executive Status Update

Senior Management of all departments

Update project status, escalation

of all risk issues

Mandatory Formal Status

Report Template

Executive Summary

Monthly Ed

Issue Management Database

All project team members.

Submit Issues as they occur

Optional Issues Database

Issues Report Template available

during weekly meeting

Weekly per the expected

action.

Tom

Phase Review Signoff

All project lead members.

Review deliverables for the phase

Mandatory Phase Review Checklist

Phase Review Report

Four phases

Joe

D. Method for Updating the Communication Plan

The communications plan will be updated as needed and reviewed during the Executive Status Meeting monthly. Any changes to the

communication will be approved by the Architecture Group manager. Any changes to the plan will by disseminated during the weekly project

team meetings and updated on the Project Status Web

E. Existing Systems

There is a weekly organizational release meeting that is held by the Architecture group. We have been invited to attend the meeting to review changes and major events to the organization. The information gathered here will be used in the project status meeting and included as

appropriate. The meeting will also address items and other systems that have an impact on us.

F. Escalation Process

The initial review of the issue or risk will occur during the project status meeting as gathered by the Issue Management Database report. The Project Status Web will be used to escalate any issues or risks not resolved during the weekly meetings. When the issue or risk is identified

in the Status Web, we will conduct a review and provide a contingency plan to the Executive Status meeting. If the issue or risk is still not

resolved, it will be assigned to an executive committee for action.