Dedication & Passion
Many believe that the pc is singing it’s last strofes. And in some cases, this is true. At least for some tasks and needs. At DataManix we have seen the light. Our portfolio of mobile solutions is actually something we are very proud of. Common to them all is that they work as the right tool in the right situation and supports your business. Otherwise it does not make any sense.
Work in a browser
The strength with the server
But what about all the systems you already use ? Do everything needs to be replaced ? No. Not at all. FileMaker is probably the strongest platform for deep integration with other solutions. Get data. Bring data. Get all the advantages of updated data in context. Some is relevant for the CEO in one context. Something else is relevant for the product manager and something third is relevant for the account manager. That is something you can trust us with.
Development process with DataManix
Development process can be different in development companies and from system to system. We work with agile development methods, which also means that we have a very close dialogue during the development phase. It also means that you as a customer, get access to the development system very early in the process so that you can test parts of the system and provide feedback continuously. It is our experience that even the most skilled and experienced project managers may find it difficult to have a complete overview of the smallest details in advance. So that we do not waste time developing elements that must be adjusted subsequently, we try to catch it during the development phase. It gives the best result in the end.
Below we have described our phases shortly.
IDENTIFICATION OF NEEDS AND ISSUES
Here we clarify needs and problems to solve. Requirements and wishes outlined.
A development description is comparable to the architect’s design for a house. This is where the individual parts of the system are described and where we can assess the extent of the solution. Often divided into several phases.
APPROVAL OF THE DEVELOPMENT DESCRIPTION
When we agree on the description and scope, you approve the development description and we make a plan for the development together.
Here we start the development with what we call detail sketches. The drawings of the individual screens, workflows drawings and functional descriptions. They form the basis for the actual development, which will start once we agree on detailed sketches. Early in the development phase, you get access to the system so that you can join and test the components continuously. This makes the process much more efficient.
When the development is complete, there will be a separate test phase, where all parts and functions needs to be tested. As you have been a part in the entire process and been testing parts during that, this phase is often a smaller task.
This is the designation for the process that happens when we put the system into operation. We might need to transfer data from old systems and there may be a need to set up connections for integration with other systems.
We develop systems that support your business and processes and you have been involved throughout the development process. Therefore, it is our experience that other colleagues is easily introduced into how the system works. Also because it is logical compared to how they work everyday. But we often find that our clients want us to make a training class for the users. It’s also a good idea to get all colleagues to feel ownership for the system. This will ensure that your company gets the full benefit of the investment.