Develop a Communication Plan
Communication requirements analysis is an investigation that leads to a clear articulation of the stakeholders’ communication needs.
- Identify stakeholders
- list all the people you will need to communicate with regularly during your project
- Capture the stakeholder’s name, title, relationship to the project, and what you need from them or what they can provide
- Identify stakeholder communication preferences
- after you have identified the stakeholders, explore options for how you can contact them
- find out
- how people prefer to be contacted
- their contact information if needed
- their time zone and typical working hours
- location
- Define the type of information they need and how much detail they prefer, and take note of how they like to consume information
- Create the project communication plan
- use your stakeholder information to create a communication plan
- This step will fill out the eight elements described on the previous page:
- goals
- stakeholders
- team members
- artifacts
- channels
- recipients
- frequency
- outcomes
- use a template
- balance the preferences of many people against a desire to limit overhead
- Share and finalize the plan
- after you finish a draft, share it with everybody involved in the final plan,
- Verify that everybody is satisfied with the plan, and make adjustments if needed
- post it somewhere accessible to the team
- update it throughout the project as communication needs change
- Schedule everything
- schedule all the meetings, and reserve the necessary resources
- Schedule the tasks needed to prepare for meetings or send other communications
- schedule meetings far in advance so that attendees are aware and can plan to attend
- Revise the Plan
- communication plan will change throughout the project’s life cycle
- Review the communication plan goals to ensure continued alignment when you have a proposed change to the plan
Example
Communication Audience Goals Schedule Format Kickoff Meeting All project stakeholders Introduce the project to stakeholders; manage and set expectations. TBD, one-time event Meeting, project charter document, presentation Steering Committee Meeting Steering committee, project leads, other stakeholders as required Review status, manage performance, clear issues. Weekly Meeting Status Report All project stakeholders Communicate current progress, issues, and risks. Weekly, at least 24 hours before the Steering Committee Meeting Report Team Meeting Project team Report status, identify issues, develop solutions as a team. Weekly, at least 24 hours before Status Report is due Meeting, project plan, status report Team Standup Dev team Quickly coordinate work for the day. Start of each business day Timeboxed standup meeting of 15 minutes Milestone Review All project stakeholders Review status, present deliverables, gather feedback, decide next steps. At project milestones Meeting, review or demonstration of deliverables Lessons Learned Project team Review successes and failures to capture improvements for future projects. At project end Meeting that produces a lessons learned document
Tips for Creating a Good Communications Plan
- A communication channel doesn’t need to be unique to your project
- leverage existing channels whenever possible, assuming the context makes sense
- Communication plans should share an appropriate amount of information
- Adapt communication plans to meet the style of your audience whenever possible
- Select an appropriate communication frequency for the project and audience
- To find out what communication channels and frequency work best for stakeholders, ask them
- create a simple survey to determine what your stakeholders need