Developing Successful Multimedia Projects

Size: px
Start display at page:

Download "Developing Successful Multimedia Projects"

Transcription

1 Developing Successful Multimedia Projects

2 Agenda Introduction Overview Phases Summary

3 Introduction Who I am Who you are Why we re here What you re going to learn

4 Why Multimedia? Print

5 Why Multimedia? Print CD-ROM

6 Why Multimedia? Print CD-ROM Web

7 Multimedia Development Methodology Purpose Provides the necessary structure for the successful implementation of a multimedia project Benefits Saves time Allows accurate cost and resource estimates Provides a common plan for all project team members

8 Six Steps to Success Requirements Concept/Design Production Testing Implementation Measurement

9 Requirements Service Agreement Before you begin gathering requirements, create a Service Agreement that contains the following information: Project description Deliverables Account responsibilities Customer responsibilities Requirements estimates Billing Special provisions Authorization Requirements schedule

10 Getting Started Build your project team. Create a Definition Workbook.

11 Definition Workbook Definition Workbook Requirements Determination Document Project Estimate Project Schedule Project Service Agreement

12 Requirements Determination Document Document the following information : Project overview Technical requirements list System architecture Content plan Screen flows Screen designs Project assumptions Considerations for future releases

13 Definition Workbook To complete the workbook, follow these steps: Determine customer needs. Make an initial pass at the Requirements Determination Document. Meet with customer to validate the document. Gather additional requirements or changes. Evaluate these changes and additions, and update the document. Repeat until the customer signs off on the Requirements Determination Document. Finalize the project schedule and estimate.

14 Requirements Determination Document Project Overview Document the following information in the Project Overview: Project description Goals and objectives Audience Primary message Financial and time restraints Other constraints Measurement Approvals Creative tone

15 Requirements Determination Document Project Overview #! & ( % $ &$ Describe the project by asking : What is the delivery platform? What information do we want to present? How/where will it be presented or used? What is the size and scope of the project? % (!!

16 Requirements Determination Document Project Overview #! & ( % $ &$ Define your goals and objectives : Goals are what you want to accomplish as a result of the project. Objectives are the steps necessary to achieve these goals. % (!!

17 Requirements Determination Document Project Overview #! & ( % $ &$ % (!! Remember your audience and their perspective: Who will be viewing and using the product? Is your audience internal or external customers? What is their age, income, education, attitudes? Are there any possible problems that could occur in communicating with this audience? Are there any current perceptions about the product/service/organization that you must overcome?

18 Requirements Determination Document - Project Overview #! & ( % $ Answer these questions about your message: What do you want your target audience to think, feel, or do as a result of the project? What do you want the primary message to be? &$ % (!!

19 Requirements Determination Document Project Overview #! & ( % $ &$ Consider these issues about the creative tone: Determine what approach will effectively deliver the primary message to your target audience. Determine whether the tone of the project needs to follow an existing theme, design, or marketing campaign. % (!!

20 Requirements Determination Document Project Overview #! & ( % Keep your project within budget and on time: Know your customer s budget. Determine the timeframe for implementation. $ &$ % (!!

21 Requirements Determination Document Project Overview #! & ( % Consider factors that impact the project: Determine what other constraints may affect the development and production of your project. $ &$ % (!!

22 Requirements Determination Document Project Overview #! & ( % $ &$ Answer questions regarding measurement: How will you measure your project s success? What data is necessary for your chosen method of measurement? How will you collect this data? % (!!

23 Requirements Determination Document Project Overview #! & ( % $ Answer these questions regarding approval: Determine how the customer approval process will work. Determine who is responsible for approving the various components of the project. &$ % (!!

24 Requirements Determination Document ( *# (! Document the functional requirements: Interface requirements Application components Additional requirements System security Usage tracking and reporting Installation requirements (

25 Requirements Determination Document ( *# (! Functional requirements (contd.: Distribution requirements Maintenance and support Indicate whether each requirement is a high, medium, or low priority (

26 Requirements Determination Document ( *# Document the system architecture: Describe what hardware and software environments are needed. Include diagrams, if necessary. (! (

27 Requirements Determination Document ( *# (! Document the content you will use: Determine what you want to say and how you will say it. Make sure you have the legal rights to use the chosen content in the chosen format. (

28 Requirements Determination Document ( *# (! Document the flow of information: Include a basic diagram of how the project will flow screen to screen. Enables your customer to see the project more clearly. (

29 Requirements Determination Document ( *# (! Document the design of the screens: Create basic representations of each screen. Make sure that your customer knows that you understand their needs. (

30 Requirements Determination Document ( *# (! Document the assumptions: List any assumptions required to complete the Requirements phase. Develop a project plan. Answer all questions about the project. Make sure all assumptions are correct; incorrect assumptions can delay a project or increase its cost. (

31 Requirements Determination Document ( *# (! Document ideas about future releases: Determine whether there are other items to consider for future releases or enhancements. Determine whether there s anything you can do now that will save you time and work later. (

32 Requirements Determination Document ( *# (! Define technical or specialized terms: Define any terms that your customer may not understand. Document these terms so that your customers won t get lost or frustrated. (

33 Definition Workbook ( *# (! ( Create the Project Estimate: Determine your resources. Decide project steps and sub-steps. Estimate how many hours each resource will spend on each phase. Determine mantime costs for each resource. Add mantime costs to hardware and software costs.

34 Definition Workbook ( *# (! Create the Project Schedule: Take the steps determined in the project estimate and assign start and end dates. Determine which tasks must precede others and which can be done at any time. Enter this information into a project management tool. (

35 Definition Workbook ( *# (! Create a Project Service Agreement: Document your service offerings, your billing policies, and the terms and agreements of the project. Use the Requirements Service Agreement to create the final Project Service Agreement. (

36 Before You Begin Perform the following tasks: Define roles and responsibilities. Review the Definition Workbook. Set up the Design Workbook. Conduct a kick-off meeting.

37 Concept and Design Activities Document the following information: Detailed thematic treatment Navigational flow chart Application technical design Script Storyboards Interface design Physical architecture Functional prototype Audio and video plan

38 Concept and Design Activities End by performing these activities: Obtain customer approvals. Update the project schedule.

39 Production Tasks Perform the following tasks: Secure assets; gather archived and outside content; obtain legal rights for use. Prepare content--create text, photographs, audio, animation, graphics, video, digitize video. Build the application architecture. Integrate the product. Perform alpha testing. Update the documentation. Obtain customer approval and update the project schedule.

40 Testing Activities Begin by conducting the following tasks: Identify beta testers. Review the test plan. Conduct beta testing kick-off.

41 Testing Activities In beta testing, perform the following activities: Set up the beta testing environment. Create and distribute the master product. Execute the test plan. Record test results. Update the database. Generate bug reports. Modify the master product. Obtain customer approval and update the project schedule.

42 Implementation Tasks Perform these activities during the Implementation phase: Create final master product. Document the distribution plan. Ship the hardware. Ship the master product. Execute the distribution plan. Update the project schedule.

43 Measurement Activities Conduct the following activities: Distribute the customer survey. Conduct a post-project review. Conduct final billing. Prepare content for archiving. Execute the archiving process. Execute the maintenance and support plan. Update the project schedule.

44 Summary To get a copy of this presentation, access the conference web site. To receive MS Project templates, send me an message : gebinger@rens rens.com

45 Introduction

46 Why Multimedia?

47 Why Multimedia?