20151009141007chapter 6-Communication
20151009141007chapter 6-Communication
20151009141007chapter 6-Communication
MMD3023
Outline
Communication
Communication
During a project we face to different changes that have
different causes. But one of the most common is an
alteration to the work specification.
The computer industry has had to developed some form
of control, this is called change control or change
management.
Communicating the changes may seem trivial, but the
team is usually an extended one in which some processes
are performed off site.
Contacting several people to communicate a change and
ensuring that they remember to carry it out is not trivial.
Even identifying the change can be problematic. Unless
each component has the identification code .
Communication
Apart from informing everyone any
documentation will need to be revised and
extra copies given out. This documentation
for multimedia project can run into several
hundred pages.
On the other hand clients need to understand
the possible consequences of changes.
So documenting the changes and reporting
the in an organized way is difficult.
Communication
Software engineers This make it clear that
recommend using a change any change needs to be
request form, which would considered by all
involved for the possible
have the following features: impact and the time for
project name implementing the
Date change to be agreed.
Change initiated by Although this form will
not be useful completely
Change description
for ever type of
Requirement affected multimedia projects but
Other program effect The similar process is
Other system effect needed in multimedia
developments.
Planned start and completion
resources affected
Approvals
Stages of a product
A product generally follows these
stages of development:
1. Agreement to the overall structure and major content
area
2. Agreement of platform for offline projects, the systems
technical capabilities for online, and product
specification for both types of project
3. Agreement to the detail of each component: text,
navigation methods/menus, audio, graphics, video.
4. Agreement that the package operates as stipulated for
phase 1.
5. Agreement that the product has fulfilled all
specifications and is concluded.
Responsibilities
Project managers To keep clients informed
responsibilities: on:
to work with the client to a) general progress
produce a mutually b) on any slippage as it
acceptable proposal that occurs and actions to be
outlines the project content,
taken to remedy it
timing and budget
c) On any suggested
To produce a detailed work
schedule consistent with
changes to the
agreed start and finish specification arising
dates, which will map out from technical or design
phases of production. factors as soon as these
occurs
To monitor and record time
spend on the project d) On any other factors that
affect the project
Responsibilities
to ensure that each part of the project is produces
to the right technical arrangement
to ensure that the structure and approach to the
program are agreed and signed off
to ensure that the content is agreed and signed
off
To agree the number of turn-around days for the
client organization for any revision
to provide deadline for the client
To get final sign off for the completion of the
project
The clients responsibilities
To prepare a clear brief for the developers
To work together on the detail of specifications
To inform the project manager of any factors that will
interrupt on the project
To keep within the accept revised time, cost, and quality
penalties
To agree that any changes made after deadlines will incur
time, cost, and quality penalties
To agree that any slippage caused by delay of any type by
the organization will incur time, cost, and quality penalties
To help the developer gain access to any people or
materials in the organization who will aid the project
Summary
Before beginning a project, determine its
scope and content.
The process of making multimedia involves
idea analysis, pre-testing, task planning,
development, and delivery.