Deployment Methodology

We often say that when IT projects fail or cause problems, it is hardly ever due to the software, but most of time because of the people. The fact that we have excellent track record in delivering our projects is not a coincidence. The secret recipe includes several factors. The two most important ones are People (competence + quality) and Deployment methodology. All our Solution Architects and Consultants are trained and work according to our Turnpikes Deployment methodology, which is a result of many years experience with ECM and VIM projects and tailored to capture the specifics of those projects.

1. Initiate


Initiate phase is the kick-off phase where project teams align and create a common understanding on the key aspects of the project and validate a project schedule.

  • Kick-off workshop to learn project objectives, priorities and align on project organization and time line
  • Customer and Turnpikes agree on how the project will be governed, incl Project Charter with roles, responsibilities, status reports, meeting frequencies etc.
project schedule illustration

Project Schedule

Project plan, aligned with customer PM on timeline, resources and priorities.

2. Requirement Analysis

requirement analysis illustration

Requirements Analysis summary

Summary of the requirements in written format.


Series of workshops (onsite and/or remote) and follow-up clarification sessions to secure a common understanding of the business requirements and discuss in sufficient detail to allow for Build of the solution. 


Secure there is a common understanding of the Minimum Viable Product (MVP) by help of Customer Use cases.

Acceptance Test Plan criteria are developed.

3. Build + Test

build + test illustration

Build + Test (iterative)

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 iterations (Sprints).  Each Sprint will have defined goal and Backlog.  

Testing and Rework based on testing feedback are integral part of each Sprint. During this phase, the involved customer project team members will be trained and prepared for their role, which is to test and validate the incremental solution build.

4. User Acceptance Test

user acceptance test illustration


System readiness, meaning transport of the solution Build from DEV/TEST into UAT. People readiness, meaning training of the UAT (super)users


Backlog will be maintained with feedback from UAT. Critical issues will be handled and fixed. Non-critical will go in Backlog of subsequent sprint (which can be deployed after go-live).

UAT sign-off

Project team will request sign-off that the solution is ready for go-live (MVP).

5. Deploy

deploy illustration

PROD Readiness

System readiness, meaning transport of solution into PROD. People readiness, meaning training of end-users and end-user guides available.


Cut-over activities, as per Deploy Schedule which will be developed and validated at end of UAT phase. Cut-over plan will include chronological steps to be performed by Customer and Turnpikes to secure smooth go-live. Start usage of PROD system.


Close attention to issues surfacing shortly after go-live.

Handover to Support

Solution is transitioned to the Turnpikes Support & Managed Services team.


Lets start a new project!

Interested in enabling your business to easily make smarter decisions. Send us a message, describing your problem area, and we will get back to you with free advice as soon as possible.