Recursion Project
3 Communications
3-1 Communications Management Plan
3-1-1 Purpose
The purpose for this document is to describe which communications need to be distributed to which groups
at what intervals. On small projects it is expedient to combine this document with the Project Team Directory.
Where there are privacy concerns, however, the two should not be mixed. Note that this is a critical
document that must be maintained. In the event the project manager is absent, the substitute project manager
should be able to quickly ascertain the communications requirements from this one document.
The purpose for this project is to demonstrate the use of the PMI methodology through a comprehensive
set of project documents.
3-1-2 Copyright
Summer 2004, Irvine, California, USA, copyright by Robert E. Perrine, PMP. Offered as is, with no warranty regarding the accuracy
or suitability of this material. Copyright reserved. You are, however free to copy and distribute these documents with the following
restrictions.
- You may not charge for use or distribution of this material.
- Your usage of this material is conditioned upon your compliance with the PMI Code of Ethics.
- All distributions must be made with the intent to further the collected wisdom of humanity.
- You may not remove my name or my copyright notices from these documents.
3-1-3 Table of Contents
Recursion Project
3 Communications
3-1 Communications Management Plan
3-1-1 Purpose
3-1-2 Copyright
3-1-3 Table of Contents
3-1-4 Guidelines
3-1-4 Revision History
3-1-4 Communications Schedule
| Who Creates This
| Who Receives This
| What is it Called
| When
| Why
| How is it Sent
| | Project Manager | All Stakeholders | Project Milestones | Monthly | To track progress and see accomplishments. | Web Site
| | Project Manager | Authors | Project Status Report | Weekly | To measure progress and check EV. | Web Site
| | Project Manager | Project Team | Status Meeting Agenda | Ad hoc | On most projects, status meetings should be regularly scheduled and generally occur weekly. Since there is little staff on this project, however, those meetings are going to occur less frequently. | Email
| | Project Manager | Project Team | Status Meeting Minutes | Ad hoc | A meeting summary should be sent after every meeting. It is possible to use the Project Status Report in place of the Status Meeting Minutes if the two can be synchronized. | Web Site
| | Designated author, administrator and reviewer | Designated author, administrator and reviewer | Change Notification | Ad hoc | To notify each other of status changes on specific documents. | Email
| | Designated author, administrator and reviewer | Designated author, administrator and reviewer | Formal Acceptance | Ad hoc | Notification that a document or set of documents has been created,reviewed, revised and formally accepted. | Email
|
3-1-5 Revision History
| Date | Author | Description
| | 4 Jul 2004 | Robert Perrine | Initial release.
| | 5 Jul 2004 | Robert Perrine | Re-oriented the Communications Schedule to landscape rather than portrait to make it more legible. Also renumbered to match the Work Breakdown Structure.
| | 6 Jul 2004 | Robert Perrine | Reformatted using revised style template.
| | 11 Jul 2004 | Robert Perrine | Converted from MS Word to Adobe InDesign
| | 17 Nov 2007 | Robert Perrine | Converted back from Adobe to html. I recommend against using Adobe products.
|
|