
Communication Requirements Analysis: Defining Stakeholder Information Needs
PMBOK v8 Definition
Communication Requirements Analysis is an analytical technique used to determine the information needs of the project stakeholders through interviews, workshops, the study of lessons learned from previous projects, and other methods. These requirements are defined by combining the type and format of information needed with an analysis of the value of that information. This technique is a core tool and technique of the Plan Communications Management process, which belongs to the Project Communications Management Knowledge Area within the Planning Process Group.
Why It Matters for the Exam
The PMI exam frequently tests your ability to distinguish between what information stakeholders need and how that information should be delivered. Expect questions where you must identify the correct tool for defining stakeholder communication needs, or where you must recognize that communication requirements are derived from stakeholder information needs combined with the value of that information. This concept appears in situational questions, definition questions, and tool-related questions throughout the exam.
Key Points to Remember (for the exam)
- Main Input: Stakeholder register and stakeholder engagement plan (contain stakeholder information and communication requirements)
- Main Output: Communications management plan (documents stakeholder communication requirements)
- Key Tool: Communication requirements analysis (analytical technique)
- Common Confusion: Confusing communication requirements analysis with communication models or methods. Requirements analysis determines what information is needed; models describe how information flows; methods describe how information is delivered.
- Critical Factor: Requirements are defined by combining type and format of information with value analysis of that information
- Sources of Information: Stakeholder register, stakeholder engagement plan, organizational charts, project organization and stakeholder responsibilities, relationships, interdependencies, development approach, disciplines/departments/specialties involved, logistics of how many people are involved
- Communication Channels: Includes one-to-one, one-to-many, and many-to-many communications
Typical PMI Exam Example
A project manager is planning communications for a large infrastructure project with 50 stakeholders from 12 different departments. The project manager needs to determine what information each stakeholder group requires, in what format, and at what frequency. Which tool or technique should the project manager use? → Communication requirements analysis. This technique combines the type and format of information needed with an analysis of the value of that information to define stakeholder communication requirements.
PMI Exam Traps
-
Trap: Confusing communication requirements analysis with communication technology selection
- Reality: Requirements analysis determines what information is needed; technology selection determines how to deliver it (e.g., email vs. meetings vs. collaboration tools)
-
Trap: Assuming communication requirements are only about frequency of updates
- Reality: Requirements analysis combines type, format, content, level of detail, AND value analysis—not just timing
-
Trap: Thinking the stakeholder register alone provides complete communication requirements
- Reality: The stakeholder register is an input, but requirements are defined through analysis that combines stakeholder information with value assessment
-
Trap: Confusing "communication requirements analysis" with "communication models"
- Reality: Requirements analysis is an analytical technique (interviews, workshops, lessons learned); communication models describe the sender-receiver interaction process
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Stakeholder Register | Input to | Contains stakeholder information and communication requirements that feed into the analysis |
| Communications Management Plan | Output of | Documents all stakeholder communication requirements identified through the analysis |
| Stakeholder Engagement Plan | Input to | Provides stakeholder engagement levels and communication needs that inform requirements |
| Communication Models | Complementary Tool | Models describe how communication flows; requirements analysis determines what information flows |
Quick Review Questions
-
A project manager needs to determine the information needs of stakeholders for a new software development project. Which analytical technique combines the type and format of information with an analysis of the value of that information?
-
What are the primary sources of information used to identify and define project communication requirements? Name at least three.
-
A project has 40 stakeholders. The project manager is deciding between weekly email updates and bi-weekly video conferences for different stakeholder groups. Which tool was used to determine these specific needs?
-
In the Plan Communications Management process, what is the relationship between communication requirements analysis and the communications management plan?
-
A project manager mistakenly uses only the stakeholder register to define communication requirements. What critical element is missing from this approach?
PMBOK v8 Reference
Section 2.5.2 - Plan Communications Management (Inputs, Tools and Techniques, and Outputs)
Note: Communication requirements analysis is listed as a tool and technique under Plan Communications Management, with stakeholder information and communication requirements defined by combining type and format of information with value analysis.