Estimating production times for screencasts and elearning

Screencasts and video based learning content are growing in popularity, and we’re seeing a rise in the number of enquiries for this type of content.

Estimating the time required to develop this type of content can vary quite considerably. The easiest way to estimate the time required is to use metrics based on the duration of the screencast or video.

A simple walkthrough of a task or applications screen can take between 10:1 (ten minutes to produce  one minute of a screencast) and 100:1. The most generally quoted figure we’ve seen is 30:1.

If you want to add audio to your screencast, this is likely to be closer to 200:1. That’s because you’ll probably need to write a script, record the audio, adjust the audio quality, add the audio to the animation, and so on.

If you want to include video of a presenter, this will make the presentation look more professional, but it will mean you’ll need to allocate more time to development and production. In this case, you’ll be looking at a ratio closer to 300:1.You can reduce the time by using avatars (images of a presenter) instead of a real presenter. Adobe Captivate comes bundled with sets of avatars to help you do this.

Another factor is the level of professionalism you want to achieve. It can take time and effort to produce high quality audio and video. Lighting, in particular, can be a challenge. Adding quizzes and exercises will also have a significant impact on the time required. Creating your own music bed (a musical background to the narration) will also increase the time required. In the past, we’ve purchased audio background music files under licence, as it saved time.

What’s your experience? How long does it take you to create this type of content. Please share your thoughts below.

How can a Technical Author find more time to write user documentation in an Agile environment?

Agile planning board Flickr Creative Commons image: VFS Digital DesignWe’ve been working on a white paper that looks at how User Assistance can be more effective and developed more effectively when you’re working in an Agile environment. The white paper should be published in the next few weeks, but here’s a sneak peek at one of the issues we discuss: the lack of time available for creating User Assistance.

Agile’s iterative release of products, and sometimes frequent changes to the functionality and the User Interface, can make it difficult to create the user documentation. The Technical Author can end up having to rework content they’ve written, delete sections on functionality that’s no longer part of the product, and add information on features that have been introduced towards the end of the project. If the Technical Author waits until the product has been completed, they can find they have very little time available for writing the user documentation.

So what can you do about this?
Continue reading