If the purpose of the product is clear, we will determine the functions and features. Simply put: determine what the product should be able to do. Often there is a very long list of functions and features from the customer. Herein it is important to make a distinction between:
– must haves
– should haves
– nice to haves
We do this primarily to prevent us from developing an extremely advanced product that will take an enormous amount of development time. By making a distinction we can determine a first version of the product. In the future, further development is always possible based on the “should haves” and the “nice to haves”.
This phase is subdivided into the UX and UI Phase.
– user Journey Map: This examines which phases the user goes through and which actions can (or can) be done during this.
– wireframing: In this phase the user journey map is i.c.m. with the functions and features translated into a sketch of all screens including functionalities.
– prototyping: In this phase the wireframe is made alive to make all functions work.
All screens originating from the UX phase are worked out in a defined design. A Design System makes designing easy and further development very efficient. If there is a change in 1 element, it is automatically implemented in all other elements of the same type.
In this phase, the above story is translated into a working product. The development process starts, this is called the back-end.
Based on the size of the project, there is a certain amount of time for developing the product. We divide this period into pieces (sprints) in which feedback is given to the customer at the end of each sprint. Here the work done is discussed and provided with feedback from the customer. This way we always know if we are on the right track. If this is not the case, we can also adjust quickly in this way.
Testing and going live!
Testing is crucial when developing software products. Of course we test everything accurately, but much is also expected from the client. Together the product is run through and looked at all functions and features. In this phase there will undoubtedly be issues that still need to be adjusted. We do this until the product is 100% satisfactory.
When we are ready, it’s time to go LIVE and launch and present the product !!
After the product is in the air, it is important that it stays that way. The maintenance phase is also of great importance with software products. This includes, among other things, fixing bugs, updating the software, developing etc.
Think of it as the periodic MOT inspection of a car. He also needs new tires now and then to continue to drive well. That’s how it works with software.
Do you have plans for a new project? Please contact us and ask for Tom.
+31 85 1303420