What do we mean when we say Deployment Methodology?
When IT fails or causes problems it is rarely due to the software, but rather because of people – or due to planning. We believe that our success can be explained by our specialized team and our deployment methodology (project approach).
We can confidently say that our people are some of the best due to their high level of competencies and focus on quality. This is also supported by our excellent track record when it comes to delivering and executing our projects.
All our solution architects and consultants are trained and work in accordance with our deployment methodology. It is a project approach that we have perfected over the years and will continuously adapt.
We have tailored the process over years of experience with capturing the specifics of implementing projects in relation to ECM and VIM.
This step includes aligning the project, creating and agreeing upon a common understanding in relation to the key aspects of the projects. A project schedule is described and approved as well.
Furthermore, workshops are given to provide some insights into project objectives, priorities, alignment of the project organization and timeline. In collaboration with the customer the following will be discussed and agreed upon:
- The person who will oversee the project
- An all-inclusive project charter with defined roles
- Status reports
- Meeting frequencies
- Other important decisions that fit the individual projects.
In the end, a project schedule is formed and aligned with the project manager on the customer side. In this project schedule the timeframe, resources and priorities will be specified and elaborated to create a transparent project plan overview.
2. Requirement Analysis
Step 2 involves a summary that provides you with the requirements in written format. This requirement analysis summary is needed to continue the process. Furthermore, a series of workshops either onsite and/or remote will be included. We furthermore provide follow-up sessions for clarification and to ensure a common understanding of the business requirements. It also allows us to discuss in detail the next step, which is the Build step.
In this step we also ensure that there is a common understanding of the Minimum Viable Product (MVP) by looking into Customer Use cases. These cases will provide an even greater understanding of the value ensured. In the end of this step, the Acceptance Test Plan criteria are developed. This guarantees that the final product will meet the business requirements of your company.
3. Build + Test
This step is an iterative process and during this phase the project team will configure and/or develop the solution based on the commonly understood requirements and MVP. This phase will be managed in sprints. When we say sprints, we mean a short, time-boxed period where our team works on the project.
Each sprint will have a defined goal and backlog. Alterations that are based on the feedback from testing are an integral part of each sprint. During this phase, the project team on the customers’ side will receive training in order to prepare for their role, which is to test and approve the project/solution being built.
4. User Acceptance Test
Initiating this step includes ensuring the system readiness and people readiness. This means that the solution, which was developed and tested in step 3, is now ready for being transported for a UAT. People then receive training on how to become users of the UAT. This provides invaluable information and feedback needed to correct any critical and non-critical issues. The critical issues will be handled and fixed. While the non-critical issues will be logged for later revision in another sprint (which can be implemented after the solution has been launched.
By the end of this step, the customers’ project team will approve of the solution and for it to be launched. There will also be structured a deployment schedule which should be validated by the end of this phase.
The final step of this process includes the production readiness and people readiness. This means preparing the system for the solution to be transported into production. As well, the training the end-users and ensuring the availability of an end-user’s guide.
As per the deployment schedule/implementation schedule developed at the end of the UAT step, the cut-over activity process will be initiated in this step. This plan will include chronological steps to be taken by both us and the customer to secure a smooth launch of the system. You as the customer can now start using the production system with the implemented solution.
We will provide continuous care, where we pay close attention to issues appearing shortly after launch. From here we do a handover to our Turnpikes Support and Managed Service team. This ensures that there is always someone to contact who is aware of your specific needs and details.