Our approach to solution implementation
Our approach has a proven track record
Usually our clients require unique capabilities, or have special solution configuration needs. So we've put together a implementation approach that has a proven track record, and that is robust and reliable. This enables us to deliver what's needed in a predictable way, on time, and on budget.
We focus on delivering value throughout the implementation process.
We use a Phased Approach to implementation
The key to our implementation methodology is a Phased Approach.
In the first phase, we work with you in a Requirements Gathering and Scoping workshop. A typical workshop is two days in duration, and is held at your offices. We need to have the project stakeholders present, along with other individuals who will be involved in the use of the Actenum solution. The workshop is an intensive session, aimed at specifying exactly what's needed, how much configuration/customization is required to meet your needs, what data sources we'll be using, how the workflow will be organized, and so on.
The workshop deliverable is a comprehensive document that describes the Scope, Objectives, and Approach (SOA) for the implementation project. The document specifies the level of effort needed for the implementation, together with project costs, and this includes the effort required from you (typically for the roles of project manager, end user, and a representative from your IT group).
Once we've obtained your sign-off on the SOA document, we proceed with the other phases of the implementation project, where we adjust our solution to meet your specific needs, and integrate it with your other IT applications.
Over the course of the project we deliver multiple releases of the solution to you. The first is a prototype, delivered within four to six weeks of the project start date. Up to three additional releases, each of which will provide additional capabilities, may be delivered before the final application is ready. The prototype release allows you to start working with the solution early on, and usually causes additional discussion around features and capabilities as you begin to exercise the functions available.
Final Acceptance and Production
Once the final version of the solution is delivered to you, an Acceptance Period of 30 days follows. During this time you'll work with all of the features and capabilities that were agreed on in the SOA document, and if any deficiencies crop up, we fix them. Once the Acceptance Period is over, you’ll be in production mode with the solution.