Functioning prototype from the beginning
Once you place an order, we will set up a working prototype for your project. As soon as your users begin to test the first prototype and try things out, it will be much easier to convince colleagues and management to support your project. Therefore, an early version of Linchpin is delivered at the beginning of the project. It may not yet match your corporate design, but most likely it is already much more powerful than your current extranet or an existing Confluence system. It includes all the add-ons that will be included in the final version. It is initially run on our servers because the deployment of the productive system and a suitable staging environment must be coordinated with your IT department, which may take some time. All installation and configuration of software, operating systems and hardware are covered by the fixed price guarantee.
Division between productive and staging system
In order to avoid downtime and to ensure the continuous operation of your Linchpin Extranet, we set up a test system in addition to the productive system. This system is a clone of the productive system with the same content and configuration, embedded in a similar system landscape. On this test system we install updates and new components and extensively test them, after which you will indicate your acceptance. Only then these changes will be integrated into the productive system.
Iterative and continuous delivery of product increments
The implementation of your project is based on the Scrum framework. The core of agile software development according to Scrum is the regular delivery of product increments to customers. The functions of the software are expanded incrementally, and with the first sprint the customer already receives a version of the software. At the end of each sprint, there is a review meeting where the development team presents the new functionalities to the customer. In addition, this agile approach allows us to take account changes to requirements that occur during the course of the project.
All of our software development processes are based on the Atlassian stack with JIRA, Bitbucket and Bamboo, and follow the continuous integration process. This supports a variety of scenarios, tested automatically in every development increment. We are happy to show you our current build plans and build pipelines from other projects.
Test system in live mode
Also in live mode, we will always be running a test and a staging system to ensure that new versions are tested extensively. In this way, updates and also comprehensive changes to the productive system are controlled and kept as short as possible.