Академический Документы
Профессиональный Документы
Культура Документы
Management
Mohammad A. Rob
Communications Planning
Communication planning involves determining the
information and communication needs of the
stakeholders, when they will need it, how it will be given
to them, and by whom
The main input to this process is communication
requirements, which includes information such as:
project organization and stakeholder responsibility relationship
disciplines, departments, and specialties involved in the project
number of people involved and their location
Document Name
Document
Format
Customer
Management
Monthly Status
Report
Hard copy
Gail Feldman,
Tony Silva
First of month
Customer
Business Staff
Monthly Status
Report
Hard copy
Julie Grant,
First of month
Customer
Technical Staff
Monthly Status
Report
Internal
Management
Monthly Status
Report
Hard copy
Bob Thomson
First of month
Internal
Business and
Technical Staff
Monthly Status
Report
Intranet
Angie Liu
First of month
Training
Subcontractor
Training Plan
Hard Copy
Jonathan Kraus
11/1/1999
Software
Subcontractor
Software
Implementation
Plan
Barbara Gates
6/1/2000
Jeff Martin
Evan Dodge,
First of month
Nancy Michaels
Information Distribution
Information distribution involves making needed
information available to project stakeholders in a timely
manner
The inputs to this process include work results, project
plan, and communication management plan
Tools and techniques include:
communication skills (oral, written, formal, informal, etc.)
information retrieval systems (drawing, presentation, test plan)
information distribution method (hardcopy, e-mail, intranet, etc.)
Information Distribution
Important considerations for information distribution:
using technology such as e-mails, telephones, Web.
Intranet can be used to make available form
templates, project documents (design, schedule, etc.)
Formal method of information distribution: includes a
PowerPoint presentation or a status report.
Informal method of information distribution: includes a
discussion over a cup of coffee
sending e-mails often to a large number people
normally have adverse effect on a project, creating a
complexity in communication
e-mail is also not a good communication mechanism
for expressing ones feeling
Performance Reporting
Reporting keeps stakeholders informed about how
resources are being used to achieve project objectives
Status reports describe where the project stands at a specific
point in time. It addresses where project stands in terms of
meeting scope, time, and cost. How long did it take to complete
a task?
Progress reports describe what the project team has
accomplished during a certain period of time. Team members
often submit weekly or monthly reports and tem leader
consolidates those reports for upper management
Project forecasting predicts future project status and progress
based on past information and trends. How long it will take to
complete a task based on the past performance
Status review meetings are used to have face-to-face
discussion, exchange project information, motivate people, and
empower people to be accountable for their work. It can be a
battleground to explode conflicts between team members
Administrative Closure
A project or phase of a project requires closure
Administrative closure consists of verifying and
documenting project results
It also allows time to collect project records, ensure that
the records reflect final specification, analyze project
effectiveness, and archive information for future use
The main outputs of administrative closure are:
project archives: A complete set of organized project records
that provide an accurate history of the project
formal acceptance: a document that the project sponsor and/or
customer signs to show that they have accepted the projects
product
lessons learned: statements written by project managers and
team members about new experiences through the project
Administrative Closure
Project archives often become handy many years after
completion of the project. When is system is upgraded,
it is important to look at the design of the system
Formal acceptance helps to end the project and avoids
dragging out project termination
In a contract situation, the buyer must legally accept the
products, so the seller can receive payment.
The project team members should prepare a lesson
learned report that should contain items such as causes
of variances (in scope, time, cost), reasoning behind
corrective actions taken, new tools and techniques used,
and personal wisdom based on the team members
experiences
Describe other important accomplishments, one bullet for each. If any issues were
resolved from the previous month, list them as accomplishments.
II.
Describe most important items to be accomplished in the next month. Again relate
to the project's Gantt chart.
III.
Issues: Briefly list important issues that surfaced or are still important. Managers
hate surprises and want to help the project succeed, so be sure to list issues.
IV.
Cover page
II.
III.
IV.
V.
VI.
VII.
VIII.
IX.
Project description
II.
Project proposal and backup data (request for proposal, statement of work,
proposal correspondence, and so on)
III.
IV.
Original and revised project plans and schedules (WBS, Gantt and PERT charts,
cost estimates, communications management plan, etc.)
V.
Design documents
VI.
VII.
Deliverables, as appropriate
VIII.
Audit reports
IX.
X.
Copies of all status reports, meeting minutes, change notices, and other written
and electronic communications