multimedia project life cycle
Download
Skip this Video
Download Presentation
Multimedia Project Management

Loading in 2 Seconds...

play fullscreen
1 / 25

Multimedia Project Management - PowerPoint PPT Presentation


  • 346 Views
  • Uploaded on

Multimedia Project Management

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Multimedia Project Management' - wsolvt


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
purpose
Purpose
  • The purpose of this Presentation is to define the life cycle of any multimedia project.
the problems
The Problems
  • Missing data.
  • changing the data.
  • Unpublished work plan.
  • Low management.
  • Due date is missing
why process
Why process ?
  • Clear Work plan.
  • Team management.
  • Monitor & Control
  • Risk management.
  • Due Date.
  • Client satisfaction.
process phases
Process Phases
  • Preparation Phase.
  • Development Phase.
  • Deliver Phase.
multimedia process life cycle
Multimedia Process life Cycle

Deliver Phase

Preparation Phase

Development Phase

project request
Project Request
  • New project should be started and initiated by a request form .
  • Approval from the higher management.
project initiation meeting
Project Initiation Meeting
  • Understanding the project details and discuss the requirements and data status.
  • Project flow chart.
project requirement document
Project Requirement Document
  • The requirement document will be the guide through the development of the project and will be a check list in the delivery form at the end of the project.
  • Requirement document should be under version control and change request process.
content gathering and data validation
Content gathering and Data Validation
  • Each project will have its forms template according to the project type.
  • It is not accepted to start the project before ensuring of the completeness of data.
  • language and scientific approval .
look and feel
Look and Feel
  • Project Design theme.
  • Acceptance form.
  • Changing in the theme is so critical Later.
  • Acceptance should be within certain time.
storyboard
Storyboard
  • Sponsor know exactly what will be delivered.
  • Technical team will know exactly what work should be done.
kickoff meeting
Kickoff meeting
  • Publish Work Plan.
  • All stakeholders of the project attending this meeting.
design and media manipulation
Design and media manipulation
  • Tasks should be assigned to the team members after ensuring that each one understood his assigned task and be informed with the due time.
development phase 1
Development Phase 1
  • Team Work Plan.
prototype
Prototype
  • Contains project screens, links, media locations and main functions
  • The prototype acceptance form should be signed.
development phase 2
Development Phase 2
  • Prototype Notes.
  • Team Work Plan Continued.
validation
Validation
  • A beta version from the project should be delivered to the sponsor for reviewing the data placement and all the media in the project.
testing
Testing
  • Testing for project final version.
documentation
Documentation
  • Project documents, reports, mails and source code should be documented for further usage or for planning to any new versions.
deliver close
Deliver & Close
  • A Final version of the project should be delivered to the sponsor.
  • Project is Closed.
change control procedure
Change Control Procedure
  • Change Request Form.
change control cycle
Change request

System Review Board (SRB)

Accepted

Changing in work plan

  • Change in Requirement document.
  • Configuration control Board (CCB)

Refused

Inform stakeholders

Process the change

Change Control Cycle
system review board srb
System review board (SRB)
  • Technical team Level meeting.
configuration control board ccb
Configuration control board (CCB)
  • CCB is the higher level of review board, it is for the strategically decision which approve or disapprove the SRB results.
  • concerns the changes that will affect the budget considerations, priorities, etc .
ad