Hi Everyone,

I am developing a project plan for E-Learning development to teach our employees how to use a new in-house software.

I have run into some problems which I believe stem from the in-house software not yet existing, and consequently the SMEs have only partial theoretical knowledge of what the system should look like, or what should happen when you click on certain buttons etc...

The in-house software doesn't yet exist but will be available (40% of total functionality) in 6 months for the SMEs to play with and then become knowledgeable about. Users who make use of this 40% functionality will need to be trained 3 months after software is first handed over to us to bug test.

Since we receive the software in stages, we will then receive another software patch in another 8 months or so which will increase the software functionality to 70% maturity, and 2 years from now the SMEs will then have had experience with both the primitive and 100% mature versions of software we are trying to create training for.

However, my main problem is a resource requirements clash when the primitive software becomes available next year and we frantically scramble to get classroom training, materials, and E-Learning designed.

A) SMEs can't really help me now to design software training (E-Learning) about a software they can't access until next year. Creating E-Learning(screenshots etc...) is especially limited right now.

B) Once the software becomes available next year - the SMEs person hours will immediately need to be devoted to bug testing / bug reporting back to the software house.

With only 2 months to create classroom training, materials and E-Learning next year, it is exactly at this point in time next year that the SMEs will first become knowledgeable about the new software and so then I will need access to the SMEs to create E-Learning / record screen captures etc...

Does anybody out there have experience with designing IT Training for a software which doesn't yet exist / is being engineered?

What in particular were you able to plan right now considering SME/screen capture limitations while the software doesn't exist? What results did you achieve while waiting for the software to become available and the SMEs to become knowledgeable?

I have created some of the theoretical/conceptual E-Learning for which screenshots aren't really required, and we have some storyboards all ready to use once the software is ready.

PS - There is 1 author - me - I'm not an SME

Your basic question can be re-worded in a much more simple manner - how does one sprint a four minute mile while carrying an package weighing in excess of 50 kg?

Here's an idea. It may not be a good idea, but keep in mind that the idea comes free of charge.

1. Abandon the concept of conventional software training that focuses on teaching which button to push when.

2. Head toward an ultimate end of having some sort of help file that guides the specific operations of the software. (Which button to push to accomplish a specific function.)

3. Establish a design for that help file that will accommodate both early and ultimate features and design of the software being developed.

4. Plan to center training around two primary aspects:
A. The functions of the software that the user will be expected to perform. (If kept at a high enough level, this aspect does not need to get down to the way to accomplish the function from the keyboard or screen.)

B. How to use the newly developed help file to access the directions for doing the desired function.

Using this approach, you can incrementally modify the "help" as the software development proceeds, and, as modifications are made to the help file, all you need to do is to notify the users of the change.

If you'd like to discuss my idea further, please contact me directly.

Thanks,

Hi L&DLarry,
We are in almost the exact situation. A proprietary application is being developed to replace an existing legacy system. Implementation is scheduled for late summer 2008. Our QA dept. is scheduled to begin full application testing in April and will done in late May. We are being asked to develop instructor-led and e-learning modules.
I haven't figured out how to accomplish the task of creating training materials and a curriculum for almost 700 users in different departments without a functioning application. We also have the added burden of some departments changing their entire work process flow as a result of the new application.
We are going to attempt to create high-level outlines and fill in the gaps as we go. If you come up with any solutions I would love to hear about them!
Good Luck!

Have you ever thouht about including prototyping content? I think that is the way to assess to a underdeveloped system. Prototyping is often treated as an integral part of the system design process.

We acurrently have a project being done and we creaet prototyping-based course to our sales person and technical support.
The tools we use are PowerPoint and PPT2Flaash Pro.

And you can read more about prototyping at
http://en.wikipedia.org/wiki/Prototyping

Larry,
I feel your pain. I went through a very similar situation last year.

As far as developing simulations, screenshots, etc for the training materials, this has to be done in modules as much as possible. Once testing modules were completed or close to complete I started creating modules of training materials. This way training progressed at the same rate as the software. I was also able to find bugs while creating the training modules so it helped in the testing process. I did have to go back and update modules from time to time but I would rather be in a crunch to update something then to have to create it from scratch.

I would also reccomend looking into a Wiki for continued to support. Once the initial training was complete and the software was implemented I met my worst enemy, "Feature Creep." Once I tied the ribbon on the training package, enhancements began coming out like crazy and it became near impossible to keep the training materials updated with all of the changes. Because of this, I am now setting up a Wiki so that our tech support staff can help keep the help materials updated. As of now, the company relies on me to keep the training materials updated but with a Wiki I can get help keeping it updated from a specified group of people or everybody. I can't wait to get the Wiki up and running.