0% found this document useful (0 votes)
9 views5 pages

Communication Management Plan

The document outlines a Communication Management Plan for the Oracle ERP project, detailing the process of planning, executing, monitoring, and controlling project communications among stakeholders. It emphasizes understanding stakeholder needs, communication frequency, and the importance of effective media for communication. The plan aims to align project objectives with stakeholder expectations and ensure timely updates on project progress.

Uploaded by

perfecttutor2010
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
9 views5 pages

Communication Management Plan

The document outlines a Communication Management Plan for the Oracle ERP project, detailing the process of planning, executing, monitoring, and controlling project communications among stakeholders. It emphasizes understanding stakeholder needs, communication frequency, and the importance of effective media for communication. The plan aims to align project objectives with stakeholder expectations and ensure timely updates on project progress.

Uploaded by

perfecttutor2010
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

1

Communication Management Plan

Student’s Name

Institution

Course

Instructor

Date
2

Communication Management Plan

The communication management planning process is one of the most essential

procedures among the stakeholders. The procedure guides the stakeholders on how to plan,

execute, monitor, and control the project communications. The role of this report is to develop a

profound communication management plan for the Oracle ERP project. In addition, the plan will

highlight the most critical elements of a communication plan including scope, type and format,

reason, and frequency of communication.

Initially, the planner needs to understand what is needed to communicate. The step

involves the development of an appropriate approach based on stakeholders’ needs and

requirements or available historical artifacts. In this phase, the planner would like to address the

project’s progress to the stakeholder. The progress is based on the stakeholder’s needs to

understand the level of completion and approximate the possible deadline for its completion.

Also, the planner needs to understand who will need to communicate. The information

will be shared among the main stakeholders. The shareholders include customers, employees,

managers, executives, and sponsors. Each member is saved on the contact list waiting for the

appropriate moment to disseminate the updates.

Besides, the planner needs to outline the frequency of communication. The choice of

frequency is dependent on the workload and different phases in the development process. The

projects are mostly executed using the Software Development Life Cycle (SDLC) –which

contains different phases. As a result, the frequency of communication will be upon the

completion of each software development phase.

Additionally, the planning involves outlining where the planner needs to communicate.

The details involve the location of the senders and receivers. In this case, there are various
3

departments in which information needs to circulate. Moreover, some remote developers and

stakeholders must be reached out by the information. Therefore, the location involves both on-

site and remote points.

Moreover, the process of communication is important. The media of communication

must be selected based on their efficiency, effectiveness, and category (interactive, push, pull). In

this case, all the categories will be used to reach out to multiple stakeholders. The interactive

media to be used include phone calls, messaging, emails, and teleconferences. The push media

will be used to communicate in the departments through letters, memos, and blogs. The pull

communication will be common among developers where different completed files will be

uploaded to file servers and databases.

Also, the main reason for the communication is to align the reports with the overall

project completion. The stakeholders need to understand the progress so that they can stay

updated. Moreover, all the project reports must be updated at the end of the communication

process. Therefore, the main goal for the planner is to ensure that the communication rationale is

sound.

The communication plan also aims at closing the gap between the project objectives and

stakeholder expectations. In light of this, updating the stakeholders on the progress will also

ensure the project is completed within the stipulated deadline. The updates might also be used to

align the stakeholder’s vision with the overall project objective. The shareholders are motivated

to keep working towards the objectives. The gaps can be evaluated by using quantifiable metrics.

The most common metric includes the completion rate, the time used, and the resources used

(Darmaningrat et al., 2019).


4

The table below provides a summary of the who, what, when, where, how, and why of

the project communication plan:

Main Question Attribute

Who The communication plan will address all the available stakeholders

including customers, employees, managers, executives, and sponsors.

What The planner would like to address the project’s progress to the

stakeholder.

When Revisited after completion of each phase in the SDLC.

Where The stakeholders are located on-site (various departments) and remote.

How Aligns stakeholders’ vision with the overall project requirements. Also,

keeps them motivated.

Why align the reports with the overall project completion.


5

Reference

Darmaningrat, E. W. T., Muqtadiroh, F. A., & Bukit, T. A. (2019). Communication management

plan of ERP implementation program: A case study of PTPN XI. Procedia Computer

Science, 161, 359-366.

You might also like