Delivering IT and e-Business Value

From the discussion above and the examples of successful risk mitigation, we can identify a number of dimensions that contribute to the ability to assess and mitigate risk in the design, development, implementation and post-implementation phases of a system's lifecycle. These factors provide the setting for an examination of various project measurement methods in Chapter 4.
The user's involvement in a project is inherent to a project's success. Such involvement is required to provide information about the business setting in which a new IT project is to be implemented. The user explains the business processes that are being automated perhaps and/or the innovative opportunity technology can provide to accomplish a task not yet surmountable. Regardless of their need to be involved, history shows that user involvement in projects is relatively negligible. Some traditional lifecycle development methodologies specify that the users are involved in the functional specification process then effectively disappear until acceptance testing. How should users be involved in the design and development process in an effective and cooperative manner? More importantly, how can users provide measurements of progress and success in the design/development process?
In order to see a project through to its end, a number of parties are required to participate. The levels of participation may vary, but the vested interest on behalf of management, key user staff and IT professionals is a necessity. These parties can contribute to the successful process...