PatSine

I finally had a chance to look at the Software Implementation Checklist for Educators from SIIA. This is a helpful document for making sure that new software is successfully integrated into the curriculum. Here are the 10 steps they recommend.

The following basic concepts underlie all effective software implementation:

1. You must have objectives before you plan.
2. You must plan before you implement.
3. You must involve all stakeholders in the planning process to some degree, and obtain their buy-in for performing their assigned responsibilities.
4. Your plan must include an evaluation component and criteria for determining success.
5. You must assign an effective leader, with appropriate decision-making authority, to manage the implementation.
6. The physical environment and equipment for the implementation must match the requirements for which the software was designed.
7. The staff involved in the implementation must receive adequate training in all aspects of the software’s use.
8. The end users of the software must have the prerequisite knowledge and skills specified for the product’s use.
9. The entire implementation must be monitored and the resulting issues resolved.
10. Each stage of implementation must be informed by the evaluation results from the previous stage.

Now, my question is why do we have to have these guidelines? Why isn't this common sense? And yet, you can find these kinds of well-thought out, formally published guidelines in every field. The report goes on to provide checklists and suggestions for making each of these steps happen, so it is very useful. The problem I see very often is that we never even get to points 1 and 2. Of course, I've also heard that most people spend more time planning for their annual vacation than they do for retirement. But that's another topic for another blog!