Development
*If you are just coming to this screen, you might want to read about ADDIE, Analysis, or Design first
During this phase of instructional design (ADDIE) we develop our instructional product and get it ready for implementation.
Prototype – From our design, we should build our prototype. This can be a screen shot or mock-up of screens that show what the final product could look like. It is very important to get client approval here before moving onto storyboard development. These should also look good – so get a graphic designer to design them if needed. These will help the developer and graphic designer in the long run when looking at the storyboards if these are done well.
Storyboard – This is the story. Each screen (or scene/action if developing a game) will be depicted. Everything we have done in design will aid in the development of the storyboards. The client should be able to look at these (and see the visual in the prototype) and have an exact idea of what the final product will look and feel like. Again, these need to be signed off on.
Development – Once the storyboards are completed, development can begin. Thus, the instructional developer, programmers, graphic artists, etc. will develop the software or instruction. This might involve one to many different deliverables depending on the type of instruction being developed (i.e., CBT, software, game, simulation, training manual, instructor guide, etc.)
System Testing – During this phase the LMS, network, etc. should be tested (if needed) to ensure that the servers and network are prepared for the implementation. This is the time that the IT team and ISDers work out any system glitches, especially if delivering this to many users. This way when implementation is ready the rollout will run without glitches. And if you’re looking to effectively build and deploy your app, you should learn more about the event based architecture business.
