---
title: "Communication requirement analysis"
subject: "ICT Project Management"
chapter: 11
key: "semester_7/ict_project_management:communication-requirement-analysis"
source: https://www.bctengineer.com/q/semester_7/ict_project_management/communication-requirement-analysis
site: BCT Engineering
---

# Communication requirement analysis

ICT Project Management · Chapter 11: Project Communication Management

- Asked in: year not given
- Answer checked by Claude Opus 5.5 (high effort) on 2026-10-14
- Page: https://www.bctengineer.com/q/semester_7/ict_project_management/communication-requirement-analysis
- Whole chapter: https://www.bctengineer.com/md/semester_7/ict_project_management/chapter-11

## Question

Explain communication requirement analysis.

## Short answer

Communication requirement analysis determines stakeholder information needs by assessing type, format and value. It uses stakeholder registers and organizational charts, and outputs a list specifying what each stakeholder needs, at what detail and frequency.

## Answer

**Communication requirements analysis** is a tool and technique of Plan Communications Management. It determines the information needs of the project stakeholders by combining the type and format of information needed with an analysis of the value of that information. Project resources are expended only on communicating information that contributes to success or where lack of communication leads to failure.

#### Sources of information for analysis
- Stakeholder register and stakeholder management strategy.
- Organisational charts and project organisation and responsibility relationships.
- Disciplines, departments and specialties involved.
- Logistics: number of people and locations.
- Internal needs (e.g. communicating within the organisation).
- External needs (media, government, contractors).

#### Steps
1. **List stakeholders** and their roles.
2. **Identify what each needs to know**: scope updates, schedule, cost status, risks, decisions.
3. **Decide the level of detail** (summary for executives, details for team).
4. **Decide the format** (report, dashboard, presentation, meeting).
5. **Check the value**: is the information useful for decisions? Omit unnecessary information to avoid overload.
6. **Determine timing and frequency**.
7. **Consider the number of communication channels**: n(n−1)/2.
8. **Validate with stakeholders**.

#### Example of analysis output
| Stakeholder | Information needed | Detail | Frequency |
|---|---|---|---|
| Sponsor | Budget and milestone status | Summary | Monthly |
| Customer | Progress, demos, issues | Moderate | Bi-weekly |
| Developers | Tasks, specs, defects | Detailed | Daily |
| Vendors | Delivery dates, specifications | Specific | As needed |

```text
Stakeholders -> Needs -> Value check -> Requirements list
```

#### Importance
- Prevents too little or too much communication.
- Ensures resources are used effectively.
- Forms the basis of the communication management plan.

**Example:** In a hospital software project, doctors need short training updates and go-live dates, while the IT team needs interface specifications; the analysis gives each group only the relevant information.

## Check yourself

The answer's key points as multiple-choice questions, with the correct option and why.

1. What does communication requirements analysis combine?
   A. Cost and schedule data
   B. The type and format of information needed with the value of that information
   C. Risk and quality data
   D. Scope and contract data
   Answer: B. It combines needed information type/format with its value. (Key point: Definition)

2. Why check the value of information?
   A. To increase the number of reports
   B. To communicate everything to everyone
   C. To avoid overload by communicating only what contributes to success
   D. To remove feedback
   Answer: C. Resources are spent only on useful information. (Key point: Value check)

3. What detail level suits executives versus developers?
   A. Detail for executives, summary for developers
   B. Same detail for all
   C. No detail for either
   D. Summary for executives, detail for the team
   Answer: D. Detail is tailored to the audience. (Key point: Detail level)

## Related in other subjects

- [Requirement gathering and analysis techniques](https://www.bctengineer.com/question.md?key=semester_5%2Fsoftware_engineering%3Arequirement-gathering-techniques) — Software Engineering, chapter 1
- [Short note: Filter and oscillator requirement in FDM](https://www.bctengineer.com/question.md?key=semester_6%2Fcommunication_systems%3Ashort-note-fdm-filter-oscillator) — Communication Systems, chapter 5, asked 4×
- [Short note: Requirement gathering methods](https://www.bctengineer.com/question.md?key=semester_6%2Fobject_oriented_analysis_and_design%3Ashort-note-requirement-gathering-methods) — Object Oriented Analysis and Design, chapter 2
- [Requirement elicitation and system behavior](https://www.bctengineer.com/question.md?key=semester_6%2Fobject_oriented_analysis_and_design%3Arequirement-elicitation-in-ooa) — Object Oriented Analysis and Design, chapter 2