Chapter 7
Chapter 7
Communications planning
Chapter Objectives
At the end of this chapter, students will be able to:
Understand the importance of project communication management
Describe project communication management processes
Understand the tools and techniques for project communication management.
1
iii. Outside resources
o Your project may depend on help or information from “outside”
resources—companies or individuals not part of the organization. These
include other divisions, subsidiaries, or offices; a vendor or separate
corporation; or a consultant.
The budget
The budget defines the company’s financial commitment, and is used to ensure
that project expenses are kept in line.
When you propose a project, you should communicate in terms of risk and likely
reward.
Approval will be granted as long as you can convince management that there is a
good chance that future profits will recapture this investment within a reasonable
period of time.
2
The schedule
The schedule defines the project, and, as long as you share it with management, it
is a useful tool for ensuring that your definition conforms to theirs.
You also need to use the schedule during the later phases of your project in
conjunction with review meetings to ensure (1) that you are on the right course
and (2) that management’s desired outcome has not changed.
The schedule improves communication with your team, and helps avoid delays.
By identifying weak links and by communicating with other department managers
and outside resources, you will avoid unexpected problems.
3
Network diagram: For team meetings, the network diagram is the most effective
communication tool. If you expect a problem in the near future, both the
explanation and the likely solution will be made easier with the use of the network
diagram.
Reporting levels
Report to the Team
o Your report to the team is a form of performance review. Since you expect
the individuals to work together under your leadership, it also makes sense
to make your report to the entire group, and at one time. The review
process itself may be ongoing, but the report is made during periodic team
meetings.
Report to Management
o Your report to management is likely to be more formal but less detailed.
o Here your concern is not with the details of execution but with whether the
project will be completed on time and within budget.
o Any problems meeting those requirements should be discussed in the
management progress report.
4
2.4. Administrative Closure
Which involves generating, gathering, disseminating, information to
formalize phase or completion?
Every project uncovers new problems, unforeseen events, and unexpected
failures. Each project, therefore, constitutes an opportunity for learning and
anticipating new risks.
Many software companies conduct a postmortem study of each project
after its completion. The postmortem includes collecting data about the
initial planned delivery dates and actual delivery dates, number of defects
discovered, qualitative information about technical and managerial
problems encountered, and suggestions for future projects.
Although this phase is the least visible in the life cycle, the company
depends on it the most for learning and improving its efficiency.
The main outputs:
o Project archives: history about projects (library)
o Formal acceptance
o Lessons learned
5
The meetings should be short and limited, or you will spend so much time
in discussion that the project will be delayed by an intended planning
process.
Meetings held with outside resources and other departments should be held
primarily to anticipate problems and overcome them.
IV. Developing a communication Infrastructure
o A communication infrastructure is a set of tools, techniques and principles
that provide a foundation for the effective transfer of information among
people.
o Two modes of communication
o Scheduled modes of communication: These include planned milestones,
such as client and project reviews, team status meetings, inspections, and
so on. These are best supported by synchronous or face-to-face
communication, such as meetings, formal presentations, video
conferences, and telephone conference calls.
o Event-based modes of communication: These include problem reports,
change requests, issue discussion, and resolution. Event-based modes
usually arise from unforeseen problems and crises. Asynchronous
mechanisms such as E-mail, groupware, and problem databases need to be
set up early, and participants need to be trained to use them. When the
number of participants is large, centralized infrastructures, such as Web
sites and bulletin boards are preferable as they make more information
visible to more people than E-mail or bilateral conversations do.