Project development

Project development

keyboard_arrow_down

Project development

Wybren Kortstra By Wybren Kortstra on November 23, 2017

Let's say you have a company with an extensive labor process. You visit and evaluate public events. During the events you write down information and make notes. Afterwards, when you are back at the office, you enter the information into a computer. You have to do all the work twice, which is something that should not be necessary. Other people told you that an app might be the solution for this problem and you decide to contact a software developer. This is where we come in.

First of all we would love to know what you and your company do. We need to know how your process works. That way we get some feeling for the situation and it enables us to assess the situation and the problem. We listen to what solution you would like and where possible make suggestions to enhance the idea. After we have evaluated all the possibilities we do a proposal with what we think is the best possible solution for you. In our proposal we factor in all the aspects that affect the system. Who is going to work with the system: experts, employees, customers? What is the working environment? For example: a phone is small and harder to operate for elderly, while a laptop in most situations is too bulky to work with.

While working out the proposal we keep in mind the users in the system, the functionalities, the different pages or views and the usability. This proposal then forms our guideline for the development of the system. This does not mean that the proposal is necessarily the product we deliver.

Feedback sessions Evolution36 During development we like to show you our progress and gather feedback. The frequency of these feedback meetings is up to you. We have an office where we can meet, but we could also come over to you. During the feedback sessions we show our progress since the last session and discuss what we do next. This gives the opportunity to evaluate the design and make changes where needed. As the product evolves, new insights are found, which could improve the product. This ensures that we can both be satisfied with and proud of the product we created together.

After we finished and delivered the product we take care of support and maintenance. In one of the next blogs you can read on how we approach this.