This is how we implement

We make sure that the employees are on the journey and prepare the organization for the new changes. Read more about how we work with change management

In this phase, we break down the requirements for specifications, we usually do this together in workshops. We believe that a picture says more than a thousand words. Therefore, most design sessions are based on graphic elements and test environments. This clarifies and minimizes the risk of misunderstandings.

Releye's development method takes place in Configuration and development. We try to configure and use existing components in the platform, to the greatest possible extent. If that is not enough, we write our own code. To ensure high quality, two developers often work together with programming and review of the code. Once we have developed a function, it is always tested before it is considered complete.

In this phase, our developers create integrations. The purpose of the integration can be to retrieve or visualize data from different sources, or to streamline a workflow where several different systems are used. The integrations are central to the solution's architecture and are built to make it possible to scale up and develop the solution over time.

At the end of each sprint, our testers check the solution and verify that everything is working properly. We automate the tests, where possible. Then we invite the entire project team to a demo. Here we show the latest features and collect feedback. The feedback is prioritized and then planned into future sprints. Test persons from the customer's side also review the solution to ensure that it looks as intended. Final tests are carried out, at the end of the project. Then the solution is tested for acceptance before it is released to the production environment.

When all parts are in place and the acceptance tests are complete, it's time for launch. The launch has been planned since the start of the project and it is now up to proof. The solution is rolled out within the organization and until everyone is on board, we have something we call "hyper care" which means that users quickly get help when needed. Before, during and after launch, we also hold training in the solution.