Our methodology

The only way we can guarantee our customers the success of their solutions and control the results is to use properly processes and maintain an organized work environment.
The Microsoft Solutions Framework is employed for developing and managing software projects from conception through to implementation.

We consider that a very important success factor is customer involvement; this is why we are very transparent in our processes and procedures so you can really watch your solution growing day after day, and feel free to step in at any time.

Using a combination of both Agile and traditional development methodologies for software development projects, we break a software project down into manageable pieces which are allocated 3-4 week long "sprints".
At the end of each sprint we present the completed software requirements to the client for review.
Client feedback is very valuable at this point and we are making all necessary changes to fit their needs.

During the development phase all these phases must be completed:

  • Envisioning
  • Planning
  • Development
  • Stabilizing
  • Deployment

Phase 1 - Envisioning

During Envisioning Phase the main business requirements are gathered and the project scope is defined. At this stage a rough cost estimate and time frame for the project is defined. These estimates will be refined during the Planning Phase. Envisioning ends when all parts involved agree on the scope (defined in terms of functionality) of the project.

Phase 2 - Planning

In the Planning Phase all the high level requirements determined in the Envisioning phase are refined and documented, the detailed project plans and technical design are developed. The Planning Phase ends when all plans, the technical design and the final cost are completed and agreed with the customer.

Phase 3 - Developing

During Development Phase we develop the technical solution according to the specified requirements. Frequent builds of the solution are developed; each build adds more features, until all the requirements are fulfilled. The advantage of frequent build is that you can participate in the development phase, and watch your solution growing. The development phase ends when all the requirements are covered by specific features and functions of the solution.

Phase 4 - Stabilizing

During Stabilizing Phase we test the solution and eliminate any errors discovered. Typical test performed during this phase are: User Acceptance and Usability Testing, Performance Testing, Integration Testing, Security Testing, and many other tests that ensure a high quality solution. This phase ends when no errors are discovered and the solution is 100% bug free.

Phase 5 - Deployment

Finally in the Deployment Phase the solution is installed in the production environment and the acceptance tests are rolled out. This phase ends with the acceptance sign-off and project review which ends the development of the current version, and we are ready for the next version. After the solution acceptance the project enters into the maintenance phase and all the knowledge is transferred to your staff or our operations, depending on your wish.

Process Tools

For optimum results, the LinkTo Software development process is managed by using last generation software tools such as:

  • Microsoft Team Foundation Server 2012
  • Microsoft Visio
  • Microsoft Project
  • Microsoft Visual Studio 2012