This is the seventh article in the series “How to remember ITTOs”. You can find all the articles in this series here: How to remember ITTOs series.
ITTO is an acronym that stands for Inputs, Tools and Techniques, and Outputs.
In this article, we will focus on Project communications management.
What is Project Communications Management?
Project communications management is the knowledge area in which the team performs the following major activities:
- Develops a plan for project communications
- Distributes project information
- Ensures communication is effective for stakeholders
Process Flow for Project Communications Management
I have suggested process flow diagrams as a way to remember and map the concepts in the previous articles. Following the same approach, I have given the process flow diagram for Project Communications Management below.
I have included ONLY the major inputs and outputs, so that it is easier to understand rather than complicating it too much. It does NOT include ALL inputs and outputs. I have included only those inputs and outputs, which I felt are significant. Please refer to PMBOK Guide for a complete list of ITTOs.
The best way to remember the ITTOs is to draw the process flow diagram yourself. It would help your mind to map the inputs and outputs to the processes; and would help to remember the process flow for a very long time.
Tips to remember ITTOs in Project Communications Management
- Organizational Process Assets (OPA) is an input to all the processes in Project communications management. (Please note that OPA is an input to 47 processes; only two processes do not take OPA as an input. They are 5.5 Validate Scope and 11.7 Monitor Risks).
- Enterprise Environmental Factors is an input to all the processes of Project communications management.
- Resource management plan and Stakeholder engagement plan are inputs to all the processes of Project communications management.
- Once communications management plan is developed in 10.1 Plan Communications Management, it becomes an input to the remaining two processes in Project communications management.
- Work performance data is an input to Monitor Communications process; and work performance information is the relevant output from this process.
- Change requests is an output of Monitor Communications process. (Note: For all Monitoring & Controlling processes, change requests is an output; the only exception is Perform Integrated Change Control. In this process, change requests is an input and Approved change requests is an output).
- Work performance reports is an input to Manage Communications process. Work performance reports is an input to only three other processes, namely, 4.6 Perform Integrated Change Control, 9.5 Manage Team and 11.7 Monitor Risks.
Conclusion
What is your approach to remember ITTOs in Project Communications Management? Do you like the above approach? Have you tried this approach hands-on? Share your experience and advice whether it helped you.
Do you have any other tips you want me to include in the above list?
Share your opinions and comments in the comments box below. I will continue to work on the process flow diagram for the other knowledge areas.
Certified Risk Management Professional (PMI-RMP)®
An enthusiastic project management practitioner and trainer.
- Yet another PMP Success Story - October 21, 2019
- Project Management Using Microsoft Excel - September 10, 2019
- PMI-RMP Course by uCertify – Is it for You? - August 3, 2019
Dhivya says
Communication is the process of providing details to that can understand or make decision out of it. So it makes a logical to link communication to the process that involves human beings, which are Resouce and Stakeholders. Hence we could see that the plans and documents related to these two KA linked to communication KA.
Manickavel Arumugam says
Yes, you have a valid point. Communication and stakeholder management knowledge area are highly interconnected and you can see lot of overlaps. In fact, stakeholder management was split from communication knowledge area and made into a separate KA only since PMBOK 5.
Vishal says
Superb explaination of the COST mgmt Knowledge Area. Please can you share similiar details for RISK, Procurement, and Stakeholder mgmt ares.
Manickavel Arumugam says
Thanks Vishal for your feedback. I will try to post the articles for the remaining knowledge area at the earliest.