Implementation project
The start-up of an implementation project is almost always a joint workshop to identify the business processes the system will support.
The business processes are usually documented with use cases, which will be the base for test cases later in the process.
The project is documented in a project plan with defined milestones.
The participants in the project are identified, a project group and a steering group are appointed. Depending on the complexity, the project can be divided into anything from 4 to 8 phases.
- Start-up
- Installation
- Data migration
- Development and Adaptation
- Integrations
- Acceptance test
- Education
- Production start
Installation
Depending on whether it’s a SaaS-solution including application hosting by iFACTS or it’s an on-prem installation, operated in your own internal IT environment, slightly different activities are required. Well-documented guides are available to help those who need to do the job.
First step is to set up a test environment in the project to make it possible for the team to work practically and verify different solutions along the way.
Data migration
iFACTS has templates to receive all historical data you want into the system. Depending on the source of the data it can be a challenge. If the data comes from another system or from excel, various issues can arise.
iFACTS has extensive experience, and is available to help with the direct contact with previous suppliers, when needed.
Development & Adaptation
iFACTS has extensive functionality with great potential for flexibility in configuration.
When new development is required, the development team, programmers and testers, work in two-week sprints with monthly releases. All development will be available within the standard product, which is then upgraded to relevant customers’ installations.
iFACTS development cycles require 3-6 months planning, depending on the size of the project.
Integrations
iFACTS has well-developed APIs for integrations with a variety of external systems. When a new integration is required, contact with the counterpart is established early. In our experience a well-executed integration is achieved by adequate planning with a clearly defined interface and requirements.
Acceptance test
iFACTS tests all functionality in recurring regression tests at every release. The customer-unique installation is tested in consultation with the customer for new releases.
The use cases identified in the start-up phase are the base for test cases for acceptance testing.
In the end, it is the customer who will make the final approval. iFACTS provides support needed in the process.
Training
iFACTS offers customized training within the framework of the project. This is often done in collaboration with the customer, as the organization often has a lot of questions about the business process and various changes to the same extent as application questions.
iFACTS' efforts are often focused on a small group of the customer, who can then continue to work internally in their organization according to the "train the trainer" approach.
Production start
Finally, it's time to get started.
A final migration is often made shortly before production starts. Sometimes you have to do without a system for a couple of days, depending on how critical the historical data is.
iFACTS can be on site for support during the start of production with the possibility of immediate support on demand.
The above process can take anywhere from 6 weeks to 4 months depending the complexity of the process.
The project resources needed depend on ambition and capacity. Either the customer can do most of the work, which can be a good way to get started in the system. Or iFACTS can offer experience and knowledge to do major parts, if the customer’s organization is lacking resources.
Get in touch with us with questions - time to get started!
