Multimedia Project life cycle<br />www.wsolvt.com<br />
Purpose<br />The purpose of this Presentation is to define the life cycle of any multimedia project.<br />
The Problems<br />Missing data.<br />changing the data.<br />Unpublished work plan.<br />Low management.<br />Due date is ...
Why process ?<br />Clear Work plan.<br />Team management.<br />Monitor & Control<br />Risk management.<br />Due Date.<br /...
Process Phases<br />Preparation Phase.<br />Development Phase.<br />Deliver Phase.<br />
Multimedia Process life Cycle<br />Deliver Phase<br />Preparation Phase<br />Development Phase<br />
Project Request<br />New project should be started and initiated by a request form . <br />Approval from the higher manage...
Project Initiation Meeting<br />Understanding the project details and discuss the requirements and data status.<br />Proje...
Project Requirement  Document<br />The requirement document will be the guide through the development of the project and w...
Content gathering and Data Validation<br />Each project will have its  forms template according to the project type.<br />...
Look and Feel<br />Project Design theme.<br />Acceptance form.<br />Changing in the theme is so critical Later.<br />Accep...
Storyboard<br />Sponsor know exactly what will be delivered.<br />Technical team will know exactly what work should be don...
Kickoff meeting<br />Publish Work Plan.<br />All  stakeholders of the project attending this meeting.<br />
Design and media manipulation<br />Tasks should be assigned to the team members  after ensuring that each one understood h...
Development Phase 1<br />Team Work Plan.<br />
Prototype<br />Contains project screens, links, media locations and main functions<br />The prototype acceptance form shou...
Development Phase 2<br />Prototype Notes.<br />Team Work Plan Continued.<br />
Validation <br />A beta version from the project  should be delivered to the sponsor for reviewing the data placement and ...
Testing<br />Testing for project final version. <br />
Documentation<br />Project documents, reports, mails and source code should be documented for further usage or for plannin...
Deliver & Close<br />A Final version of the project should be delivered to the sponsor.<br />Project is Closed.<br />
Change Control Procedure<br />Change  Request Form.<br />
Change Control Cycle<br />Change request<br />System Review Board (SRB)<br />Accepted<br />Changing in work plan<br />Chan...
System review board (SRB) <br />Technical team Level meeting.<br />
Configuration control board (CCB) <br />CCB is the higher level of review board, it is for the strategically decision whic...
Upcoming SlideShare
Loading in …5
×

Multimedia project life cycle - wsolvt

2,293 views
1,947 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,293
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
36
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Multimedia project life cycle - wsolvt

  1. 1. Multimedia Project life cycle<br />www.wsolvt.com<br />
  2. 2. Purpose<br />The purpose of this Presentation is to define the life cycle of any multimedia project.<br />
  3. 3. The Problems<br />Missing data.<br />changing the data.<br />Unpublished work plan.<br />Low management.<br />Due date is missing<br />
  4. 4. Why process ?<br />Clear Work plan.<br />Team management.<br />Monitor & Control<br />Risk management.<br />Due Date.<br />Client satisfaction.<br />
  5. 5. Process Phases<br />Preparation Phase.<br />Development Phase.<br />Deliver Phase.<br />
  6. 6. Multimedia Process life Cycle<br />Deliver Phase<br />Preparation Phase<br />Development Phase<br />
  7. 7. Project Request<br />New project should be started and initiated by a request form . <br />Approval from the higher management.<br />
  8. 8. Project Initiation Meeting<br />Understanding the project details and discuss the requirements and data status.<br />Project flow chart.<br />
  9. 9. Project Requirement Document<br />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.<br />Requirement document should be under version control and change request process.<br />
  10. 10. Content gathering and Data Validation<br />Each project will have its forms template according to the project type.<br />It is not accepted to start the project before ensuring of the completeness of data.<br />language and scientific approval .<br />
  11. 11. Look and Feel<br />Project Design theme.<br />Acceptance form.<br />Changing in the theme is so critical Later.<br />Acceptance should be within certain time.<br />
  12. 12. Storyboard<br />Sponsor know exactly what will be delivered.<br />Technical team will know exactly what work should be done.<br />
  13. 13. Kickoff meeting<br />Publish Work Plan.<br />All stakeholders of the project attending this meeting.<br />
  14. 14. Design and media manipulation<br />Tasks should be assigned to the team members after ensuring that each one understood his assigned task and be informed with the due time. <br />
  15. 15. Development Phase 1<br />Team Work Plan.<br />
  16. 16. Prototype<br />Contains project screens, links, media locations and main functions<br />The prototype acceptance form should be signed.<br />
  17. 17. Development Phase 2<br />Prototype Notes.<br />Team Work Plan Continued.<br />
  18. 18. Validation <br />A beta version from the project should be delivered to the sponsor for reviewing the data placement and all the media in the project. <br />
  19. 19. Testing<br />Testing for project final version. <br />
  20. 20. Documentation<br />Project documents, reports, mails and source code should be documented for further usage or for planning to any new versions. <br />
  21. 21. Deliver & Close<br />A Final version of the project should be delivered to the sponsor.<br />Project is Closed.<br />
  22. 22. Change Control Procedure<br />Change Request Form.<br />
  23. 23. Change Control Cycle<br />Change request<br />System Review Board (SRB)<br />Accepted<br />Changing in work plan<br />Change in Requirement document.<br />Configuration control Board (CCB)<br />Refused<br />Inform stakeholders<br />Process the change<br />
  24. 24. System review board (SRB) <br />Technical team Level meeting.<br />
  25. 25. Configuration control board (CCB) <br />CCB is the higher level of review board, it is for the strategically decision which approve or disapprove the SRB results.<br />concerns the changes that will affect the budget considerations, priorities, etc . <br />

×