Groupware, Workflow and Intranets: Reengineering the Enterprise with Collaborative Software

Implementation the final development and deployment of a system is built on successful completion of previous stages of the project. So it could be thought of as straightforward since many technical problems will already have been dealt with. However, there are significant non-technical factors which are important at this stage. Understanding how people will be affected by the new system, why they may resist change and how they can be encouraged to use the system is critical. We consider how resistance can be countered by encouraging user involvement throughout the project.
The scope of implementation is described here to include all activities necessary to get the system up and running and on the user's desktop after the system has been designed. This includes technical work such as configuration, coding, database population, testing and documentation which are collectively termed the build process. It also includes management activities such as procuring kit and managing the change in the organization that is associated with the bringing the new system in. Finally, it includes methods of deploying the software once everything else is in place.
Here we cover both technical and non-technical aspects of implementation. Since human factors are so important and sometimes neglected these are considered first. This includes particular problems with introducing groupware into the organization. Then the importance of prototyping in involving users is covered. We then go on to consider the specific problems of implementation such as testing and planning deployment. Finally, general guidelines for avoiding failure...