A Project Management Methodology for Multimedia Projects
Analysis of Existing Strategies and Creation of a New Concept
- Art: Diplomarbeit
- Autor: Stefan Hartweg
- Abgabedatum: Februar 2002
- Umfang: 133 Seiten
- Dateigröße: 707,6 KB
- Note: 1,4
- Institution / Hochschule: Fachhochschule Furtwangen Deutschland
- ISBN (eBook): 978-3-8324-5426-5
-
ISBN (Paperback) :
978-3-8324-5426-5 P - ISBN (CD) :978-3-8324-5426-5 CD
- Sprache: Englisch
- Prämierung:
- Arbeit zitieren: Hartweg, Stefan Februar 2002: A Project Management Methodology for Multimedia Projects, Hamburg: Diplomica Verlag
- Schlagworte: Internet, Web, digitale Medien
In den Warenkorb
48,00 €
Diplomarbeit von Stefan Hartweg
Abstract:
This paper tries to define a concept for managing multimedia projects efficiently and takes the suitability of existing methods into account.
Developing a valid solution makes it necessary to look at project management as a generic discipline first and then apply the results to the multimedia discipline. Only then can we be sure that no important aspects of project management have been forgotten, nor that existing and working strategies, which could be applied to multimedia projects, have been ignored. This paper therefore defines project management and generally describes its areas of responsibility. The question of whether project management is necessary and beneficial needs to be addressed as well. After project management and the necessity to actively apply it in some form has been understood in general, a specific focus on the existing information for multimedia project management will be undertaken. It will become apparent that different viewpoints exist as to whether multimedia project management should apply project management methods of related industry areas, such as software development. This will justify the need to compare multimedia projects with software development projects.
After having gained an insight into project management as well as the characteristics of multimedia projects, it is possible to determine the demands that a project management method needs to be able to meet, to successfully manage multimedia projects. It would be beyond the scope of this thesis to analyse every existing method. Instead, one method will be analysed as an example. The useful aspects of the analysed method will be identified along with its shortfalls in relation to multimedia development. Finally, recommendations on how the shortfalls could be corrected will be made, so that a project manager will be able to use the examined method, specifically suited to multimedia projects.
Table of Contents:
| 1. | Preface | 7 |
| 2. | Introduction | 9 |
| 2.1 | The Topic of this Thesis | 9 |
| 2.2 | Hypotheses and Findings | 12 |
| 2.3 | Definition of Multimedia | 14 |
| 2.4 | Types of Multimedia Products | 16 |
| 2.4.1 | Forms of Delivery | 16 |
| 2.4.2 | Categories of Multimedia Products | 18 |
| 2.4.3 | Conclusion | 20 |
| 2.5 | Project Management Definitions | 21 |
| 2.5.1 | Project and Project Management | 21 |
| 2.5.2 | Project Stakeholders | 22 |
| 2.5.3 | Project Methodology, Methods and Processes | 22 |
| 3. | The Historical Development of Project Management | 25 |
| 3.1 | The Philosophy of Ancient Project Management | 25 |
| 3.2 | The Philosophy of Modern Project Management | 26 |
| 3.3 | Conclusion | 28 |
| 4. | The Components of a Project Management Method | 29 |
| 4.1 | The Project Management Context | 30 |
| 4.2 | The Project Life Cycle | 32 |
| 4.3 | Project Processes | 32 |
| 4.3.1 | Project Integration Management | 35 |
| 4.3.2 | Project Scope Management | 36 |
| 4.3.3 | Project Time Management | 37 |
| 4.3.4 | Project Cost Management | 37 |
| 4.3.5 | Project Quality Management | 37 |
| 4.3.6 | Project Human Resource Management | 38 |
| 4.3.7 | Project Communications Management | 38 |
| 4.3.8 | Project Risk Management | 39 |
| 4.3.9 | Project Procurement Management | 39 |
| 4.4 | Conclusion | 40 |
| 5. | The Necessity of Project Management | 42 |
| 5.1 | The Subconscious Management of Projects | 42 |
| 5.2 | The Single Point of Responsibility | 43 |
| 5.3 | The Advantages of a Project Management Method | 46 |
| 5.4 | Conclusion | 49 |
| 6. | Existing Information on Multimedia Project Management | 50 |
| 6.1 | Interviews | 50 |
| 6.1.1 | Redefine | 51 |
| 6.1.2 | DCG | 54 |
| 6.1.3 | Griffith University | 55 |
| 6.2 | Published Materials | 57 |
| 6.2.1 | Managing Multimedia: Project Management for Interactive Media | 58 |
| 6.2.2 | Managing Multimedia Projects | 67 |
| 6.2.3 | Developing Effective Websites: A Project Manager’s Guide | 70 |
| 6.3 | Internet | 72 |
| 6.4 | Conclusion | 73 |
| 7. | The Suitability of Existing Methods for the New Concept | 76 |
| 7.1 | Differences Between Traditional Projects and Multimedia Projects | 76 |
| 7.2 | Software Development Management | 79 |
| 7.3 | Conclusion | 83 |
| 8. | The Development of the New Concept | 85 |
| 8.1 | The Choice for the Method | 85 |
| 8.2 | Multimedia Pathways | 86 |
| 8.3 | Alterations on Multimedia Pathways | 90 |
| 8.3.1 | The Life Cycle | 90 |
| 8.3.2 | The Processes | 94 |
| 9. | Critical Reflection on the Findings | 123 |
| 9.1 | The Quality of the Findings | 123 |
| 9.2 | What Else Would Need to be Done? | 125 |
| 10. | Bibliography | 129 |
| 10.1 | Books | 129 |
| 10.2 | Internet Resources | 131 |
| 10.2.1 | WebPages | 131 |
| 10.2.2 | Electronic Publications | 131 |
| 10.2.3 | Newsgroups | 133 |
| 10.2.4 | E-Mail Contacts | 133 |
This categorization makes it obvious that the method deals not only with project management oriented activities, but also with development-oriented activities. The structure of the categories is confusing in so far, that the development category describes the tasks needed to be performed by the development team, whereas the responsibilities of the project manager have been split into the categories of management and support. Furthermore, the term task in its original meaning suggests that it is identified what has to be done, but it does not necessarily define, the inputs necessary to perform the task, and what the results of the task will be. This problem can be found in the Multimedia Pathways manual as well. Some of the tasks have mere descriptive character, without providing information on the required input, i.e. what or who is necessary to perform the task. This is further aggravated by the fact that the development tasks cannot be project management processes, but serve as input for them at best. Parts of the project management and support tasks include a short description regarding the requirements to fulfil the task and link to a template as a tool for performing the task. [...]
For multimedia development, an iteration of all the stages of a life cycle does not seem to make sense, which requires the existing Multimedia Pathways life cycle to be adapted. This will be further set out in the following chapter. Further, the processes of the method may need to be adapted according to the life cycle application. If an iterative approach is chosen and one or more stages are looped, than the number of applied processes as well as the effort that has to be put into the processes is likely to change. Each stage of the life cycle is then described by the manual, with regards to the tasks that need to be performed. The tasks are categorized in the areas of Development, Management and Support. These areas of activity are further split into sub-categories141 (refer to Table 1). [...]
The term waterfall is used, as “(...) the flow of activity appears to cascade down the diagram of the model”121. The linear, non iterative phases of traditional project management are not suitable for multimedia development, as the stages of specification, conceptualization and production can not be separated that distinctly. In construction projects, a cost estimate for the project will usually not be given until the design, i.e. blueprints of the building, have been agreed upon. In addition, it is not until after the costs have been agreed on, that the actual production starts. Cost estimates are rather reliable, as the biggest cost factor is the material required to build the object, and material requirements can be determined rather precisely with the help of the blueprints. In construction projects, the design team, i.e. the architects, is usually separate to the construction team, i.e. the builder. There is also a clear separation of responsibilities: the builder is responsible for building the construction according to the blueprint, within the agreed budget and timeframe. The designer is responsible of making sure the construction is built to the agreed standards and quality and has to handle change requests.122 In contrast, in multimedia projects, the processes of specification and development are not as clearly separated. Cost estimates usually have to be given early in the project, where not enough information is available to accurately predict the costs of the project. Also, a mere blueprint of the product, i.e. the specification description, is not enough to develop a successful product. The specifications need to be translated into concept designs, draft versions and prototypes, which then need to be tested to make sure that the product, will conform to the expectations and needs of the client or user. This is because multimedia products are far more complex than construction projects, not necessarily to develop, but to convey the idea of the finished product to the client in the early stages of the project. In a [...]
In den Warenkorb
48,00 €
Link zur Arbeit:
http://www.diplom.de/ean/9783832454265
Arbeit zitieren:
Hartweg, Stefan Februar 2002: A Project Management Methodology for Multimedia Projects, Hamburg: Diplomica Verlag
Schlagworte:
Internet, Web, digitale Medien



