TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
I completely agree with you. My CBT developer told me that 100 to 300 hours
of development for every hour of CBT is the norm. The high end is when you
have to develop content, lower end if you don't. For this project, we are
developing ALL the content, so high end is expected. Just not possible in
the
time available. Not even if we did not sleep for the entire 4 weeks. And we
like sleeping, at least a little.
I told the client that it simply could not be done. I countered with a
demo-like click thru that shows 2 or 3 areas in detail. That we can do and
do it really well. But to develop a full blown CBT is not going to happen,
even if we all really want it to. And I will not promise what I know cannot
be done or can only be done badly. Why upset the client AND screw my crew?
Not good.
They will make a decision next week on what I said we CAN do in the time
available, which is not that much. But it is better than nothing, and more
than most companies could do!
Thanks for the reality check.
sharon
Sharon Burton-Hardin
Anthrobytes Consulting
909-369-8590
www.anthrobytes.com
Vice-president, Programs of the Inland Empire chapter of the STC
www.iestc.org
| Hi Sharon ---
|
| If this were only a document set, I'd agree with Andrew and encourage you
to
| take the business. However, having designed, developed, and produced a
CBT
| (albeit larger than the one you described), I'm thinking that it would be
| very difficult to complete a useful CBT in 4 weeks. Please note that I
used
| the word "useful" in my previous sentence. :) This post focuses on the
CBT
| portion of your Reality Check.
|
| Depending on what the client expects from the CBT, it could simply be a
| matter of presenting information you're creating for the user guide
anyway,
| or it could turn into a complex presentation that requires your team to
put
| more time and expertise into it than they may be able to provide.
|
| For example: Does the client want to include any kind of testing? If so,
do
| they want test questions throughout the CBT or one test at the end? Does
| the testing need to be scored and recorded? Any or all of these
additions,
| not to mention many others, can add many unexpected hours to the CBT
| development.
|
| As I remember, the industry standard for CBT creation is:
| 75 development hours = 1 hour of basic CBT (that is, no audio, no video,
no
| animation). That's almost two weeks to create the CBT if it is only an
hour;
| however, I believe that number assumes that the content already exists,
and
| that you have an experienced CBT team of about 10 people working on it. I
| don't have the resource for that calculation right offhand, but I'll try
to
| find it if someone wants to debate it with me. :)
|
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Attention ForeHelp and Doc-to-Help Users! Upgrade your existing product to
RoboHelp for only $299, through January 31st. RoboHelp can import your
existing Help projects! Learn how else RoboHelp can benefit you. www.ehelp.com/techwr
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
