|
Implementation Methodology
Achiever Anyware is implemented using the Achiever Implementation Methodology (AIM). Firmly grounded in best practice principles from trusted industry standard project management methodologies and incorporating over 15 years experience of successful Corporate Information Management solution implementations, AIM is customised to suit the individual needs of each customer and project.
AIM ensures that each customer gains optimum benefits from its Achiever Anyware solution by focusing on understanding its business objectives and key drivers for implementing the software in order to create a solution more closely aligned with its organisational needs.
Implementing in phases
Within the Achiever Implementation Methodology are a number of key phases that are used for measuring and managing quality control within a project. There are a number of key deliverables within each phase that must be agreed and met before progressing to the next phase. The five key phases within each Achiever Anyware project are:
Achiever has produced a Welcome Pack series that will assist and guide customers through each phase of the project ensuring the customer's project team are adequately prepared. As with any implementation of business critical software, it will require investment in time and resources. The dedicated Solution Delivery Consultant is there to help customers brief and prepare the nominated project team for the Achiever implementation and take the customers step-by-step through each phase of the process.
Initiation
The Initiation phase of the project covers project team introductions, confirmation of project scope, introduction and agreement on the implementation approach and methodology used and the creation of an initial project plan. Any project risks or constraints will also be highlighted and documented in this phase.
Definition
The Definition phase of the project examines the business objectives, critical success factors, business processes and high-level data, integration and reporting requirements to produce the Terms of Reference (ToR) document. The ToR document must be agreed and signed by the customer prior to commencing the Design phase and is used at the completion of a project by Achiever and the customer as a checklist for the completed system.
The Change Control process is implemented post ToR sign-off to restrict scope creep and potential delays to the project.
Design
The Design phase of the project includes a Detailed Requirements Gathering exercise with the customer's nominated project team to identify and understand the customer's in-depth system requirements including data, reporting and integration needs. . The System Requirements document is produced from the findings and presented to the customer's team for sign-off. This document is used to build the system. The Build phase will not commence until the System Requirements document has been agreed and signed by both parties.
Build
The Build phase of the project is when the system is configured to suit the requirements outlined in the System Requirements document. During this phase the customer's project team will continue to be involved in attending system demonstrations to provide feedback on any changes or issues identified. In addition, formal user acceptance training and testing will take place on the completed system. If data is being transferred from existing systems a sample data import will be carried out in this phase. Any integration work or required reports will also be completed in this phase.
Once the configuration work has been completed the final system will be presented to the customer's project team for final sign-off before commencing the Go Live and Review phase.
Go Live and Review
The Go Live and Review phase covers the Train the Training sessions, the live data import and the Go Live and Hand holding day. Typically Achiever undertakes a Train the Trainer approach to promote greater system ownership and improve knowledge transfer. Training materials are provided in soft-copy for the customer's nominated trainers to use in their internal training sessions and for the customer to maintain as the system evolves.
A Go Live and Hand holding day is included as part of every project to provide the customer's project team with assistance as required during the Go Live period.
The Support Process will commence allowing the customer's nominated System Administrators to raise issues on the on-line customer portal.
On average 3 months post go live a review is carried out with the customer's project team to evaluate progress and ensure that the system is continuing to deliver business benefits.
|
