Planning- Project Management Plan
- Change Management Plan
- Project Roadmap
- Scope Management Plan
- Requirements Management Plan
- Requirements Documentation
- Requirements raceability Matrix
- Project Scope Statement
- Work Breakdown Structure
- WBS Dictionary
- Schedule Management Plan
- Activity list
- Activity attributes
- Milestone list
- Network diagram
- Duration estimates
- Duration estimates worksheet
- Project schedule
- Cost management plan
- Cost estimates
- Cost estimating worksheet
- Cost baseline
- Quality management plan
- Quality metrics
- Responsibility assignment matrix (RAM)
- Resource management plan
- Team charter
- Resource requirements
- Resource breakdown structure
- Communications management plan
- Risk management plan
- Risk register
- Risk report
- Probability and impact assessment
- Probability and impact matrix
- Risk data sheet
- Procurement management plan
- Procurement strategy
- Source selection criteria
- Stakeholder engagement plan
Communications management plan
The communications management plan is a component of the project management plan. It describes how project communications will be planned, structured, implemented, and monitored for effectiveness. Typical information includes:
- Stakeholder communication requirements
- Information
- Method or media
- Time frame and frequency
- Sender
- Communication assumptions and constraints
- Glossary of common terminology
In addition, the communications management plan can include resources, time, and budgets asso- ciated with communication activities, methods for addressing sensitive or proprietary information, and methods for updating the communications management plan.
The communications management plan can receive information from:
- Project charter
- Requirements documentation
- Resource management plan
- Stakeholder register
- Stakeholder engagement plan
It provides information to:
- Stakeholder register
- Stakeholder engagement plan
The communications management plan is an output from process 10.1 Plan Communications Management in the PMBOK® Guide – Sixth Edition. It is updated periodically throughout the project as stakeholders are added and leave the project and as communications needs emerge and shift.
Tailoring tips
Consider the following tips to help tailor the communications management plan to meet your needs:
- When multiple organizations are working on a project there will be additional information needed, such as:
- Person responsible for authorizing release of internal or confidential information
- How different communication hardware, software, and technologies will be addressed to ensure information gets to everyone regardless of their communication infrastructure
- If you have a multinational team your plan will need to account for the business language, currency unit of measure, translation, and other factors required to ensure effective communication across multiple countries and cultures.
- On a project that has a significant communication component you will want to identify the resources allocated for communication activities, the time requirements, and the budget allocated.
- For projects with complex communication needs, include a flowchart of the sequence of communication events.
Alignment
The communications management plan should be aligned and consistent with the following documents:
- Project schedule
- Stakeholder register
- Stakeholder engagement plan
| Document element | Description |
| Stakeholder communication requirements | The people or the groups of people who need to receive project information and their specific requirements |
| Information | Describe the information to be communicated, including language, format, content, and level of detail. |
| Method or media |
Describe how the information will be delivered; for example, email, meetings, web meetings, etc. |
| Time frame and frequency | List how often the information is to be provided and under what circumstances. |
| Sende | Insert the name of the person or the group that will provide the information. |
| Communication constraints or assumptions | List any assumptions or constraints. Constraints can include descriptions of proprietary, secure, or sensitive information and relevant restrictions for distribution. |
| Glossary of common terminology | List any terms or acronyms unique to the project or that are used in a unique way. |
