Company Name
Program Codename
-------------------------------------------------
Communication Plan
Program ID: ##
Prepared by:
Date:
Program Team
Approval Signatures
Name: | | Name: | Title: Program Sponsor | | Title: Program Manager |
Name: | | Name: | Title: Technical Lead | | Title: Business Lead |
Name: | | Name: | Title: | | Title: |
Template Revision History Revision History | Revision | Date of Release | Owner | Summary of Changes | 1.0 | 07/4/14 | PMO | Initial Release |
Revision History Approvals Revision History | Version # | Date of Release | Owner | Comments | | | | | 1.
Introduction
* Purpose The intention of this Communication Plan is to document and manage all communications throughout the Program life cycle, indicating the what-who-when-why-how involved in program communications. This document will capture all communications required for the <Program Name> Program stakeholders. This document will also encompass all written and oral communications that take place during the Program lifecycle. This Communication Plan will be an integral part of the overall Program Management Plan and will be a staple reference document in the <Program Name> Program. * Scope
Enter text here * * References * Program Centralized Document Repository
Enter text here * * External References
Enter text here * Document Maintenance
Enter text here
2. Participants Roles and Responsibilities This section will include all of the roles and responsibilities of the <Program Name> 3. Program Structure Insert Organizational Chart(s)
4. Steering Committee This section will include all of the roles and responsibilities of the <Program Name> Steering Committee 5. Program Sponsor This section will include a summary of the Program Sponsor’s role in the <Program Name> 6. Program Director This section will include a summary of the Program Director’s role in the <Program Name> 7. Program Manager This section will include a summary of the Program Manager’s role in the <Program Name> 8. Technical Program Team This section will include a summary of the Technical Program Team’s role in the <Program Name> 9. Stakeholder Identification
Name | Title | Program | Contact | Role | Comments | | | | | | | | | | | | |
10. Communication Process * Informal * * Formal * Status Meetings * * * * Status Reports by Phase Phase(s) | Defining | Initiation | Planning | Execute | Monitor & Control | Closure | Deliverables | | | | | | | Requirements | | | | | | | Material ordering | | | | | | | Material delivery | | | | | | | Code development | | | | | | | Code delivery | | | | | | | Testing start | | | | | | | Qualification | | | | | | | Release to Manufacturing | | | | | | | Final Configuration | | | | | | | Shipment to Customer | | | | | | |
1.1 Program schedule
1.2 Budget and cost tracking
1.3 Program status on major activities
1.4 Status of issues and risks
1.5 Health status
1.6 Status of action items
11. Communication Management
Communication Distribution
Enter text here
Communication Tracking and Storage
Enter text here Communication Changes
Enter text here
12. Communication Schedule
Communication | Owner | Distribution List | Purpose of Communication | Phase | Frequency | Method | Program Plan | Program Manager | Program Team, PMO | To define the program background, scope, roles and responsibilities, any identified risks, work to define the schedule, determine staff, how communication will occur and how to close the program. | Initiation | This is to occur at the start of the Program | Email | Program Schedule | Program Manager | Program Team, Sponsor, Customer, PMO | Use this to mark key milestones and tasks with their assigned resources. | Planning | As Needed | Email | Kick Off Meeting | Program Manager | Program Team, PMO | This meeting will be used to generate goals and objectives for the program. It will also further define each member’s roles and responsibilities. | Planning | This is to occur at the start of the Program | Meeting | Weekly Status Meeting | Program Manager | Program Team, PMO | Weekly meeting to discuss issues or concerns to the program | ALL | This is to occur Weekly | Meeting | Program Sponsor Meeting | Program Manager | Program Sponsor, PMO | Monthly meeting that will help to communicate any risk or issues to the schedule and deliverables to the program. | ALL | This is to occur Monthly | Meeting | PMO Status Meetings | Program Manager | Program Manager, PMO | Quarterly meeting to report in the overall program status and gain feedback to bring back to the team | ALL | This is to occur Quarterly | Email, Meeting | Status Reporting | Program Manager | Program Team, Sponsor, Customer, PMO | Report Program progress, milestones, status, risks and issues, etc. | All | This is to occur Weekly | Email | Change Requests | Stakeholders | Program Staff, Program Sponsor, Program Manager, PMO | This will be used to add or remove scope requirement changes. | Execute Monitor & Control | As needed; but should be reviewed during weekly status meetings | Email, Meeting | Program Scope Review | Program Manager | Program Staff, Program Sponsor, Program Manager, PMO | Will be used to generate the complete scope of the program | Planning | This is to occur at the start of the Program | Email, Meeting | Program Quality Report | Program Manager | Program Staff, Program Sponsor, Program Manager, PMO | Audit stage that will be leveraged to ensure the program is meeting all targets | Monitor & Control | This is to occur quarterly | Email | Budget Review | Program Manager & Finance | Program Staff, Program Sponsor, Program Manager, PMO | Used to gain approval of budget for the program | Planning | This is to occur at the start of the Program | Meeting |
13. 14. General Information
Acronyms
Acronym | Description | PM | Program Manager | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
15. Glossary Term | Definition | | | | | | | 