The implementation steps are as follows:

1. Select roles (april)

While some of the role selctions may be more obvious than others, it is important that process leadership be determined to set the tone for implementation and ongoing process develpment.

2. Implement base transaction system (may)

Sooner than later. Much of the design hinges around a single interface and view of all pending work. The minimal requirements to launch this application using existing components should be implemented. Kitchen sink development should be avoided.

3. Create review and work forums (june)

A work forum, or process meeting, should be routinely held by the process manager to review the status of installation projects and work out problems to avoid excess delays. This is the what do we need to do? meeting.

A process review group should be assembled with representation from various roles. This group works with the process manager to report on the process transition, pass on feedback and assist in ironing out process glitches. This may evolve into an ongoing and perhaps less routine process maintenance forum where process problems are discussed.

Other forums for discussion already exist and should be used where applicable to avoid excess overlap. *mg meetings for significant process and/or service changes. Integration meetings for issues pertaining to technology proposals or infrastructure issues.

4. Pilot test

Begin a pilot test in july to divert requests through the transaction interface.