We help you to stay up to date
Especially the digital world is moving faster and faster. Requirements change permanently. Only if you can bring your idea into the market fast and close to the customer you will succeed against the competition. This is particularly true for innovations in the field of digitalization. With a wide range of services, tailored processes and methodologiese we support you to reduce your development times and to stay flexible
With more than 30 years experience and a wide range of services we are the perfect partner in the field of software solutions and data management - throughout the entire lifecycle of your project. We support you with your digitalization as well as wiith the modernization of your systems. From the first constulting up to the implementation and maintenance.
Conception & Specifications
The idea is only the first step. Together with you we develop a project concept which fits to your requirements. With a solution specification, a project plan and the right methodology.
3rd Level Support & Software-Maintenance
Our developers take care of the 3rd Level Support for your software which we have developed. We also help you to find a suitable partner for the 2nd Level Support.
We modernize your legacy system or support your keeping your application up to date with low efforts. For more efficiency, satisfied employees and for greater innovative power.
Each project and each organizationi is individual. Therefore we have differen development procesess which we can use or even combine - always in close alignment with your requirements. This means: Agile is not a panacea for us. We work as agile as it fits to your project and your organization.
We have an agile corporate culture belive in the benifits of agile prcedures in many cases. However, this doen´t mean we always have to strictly comply to all agile proceeses of Scrum. Sometime traditional approaches gain from agile aspects. To define the right way we align closely with you and your organization.
Agile software development SCRUM
We not only develop our own product RIAS according to Scrum but also many customer projects. With it we can implement change requests more flexible if necessary and align the software closer to your needs.
Our employees have mastered several Scrum projects and are trained - up till Scrum-Master.
Traditional waterfall model
Linear step by step. Everytime after one of the five to seven development phases is finised the next phase follows. In some caes an agile approach is not the right was, rather a tradtional waterfall - e.g. if the users or the business partners don´t have the capacity to give feedback on a regular basis or the requirements are already documented in a very detailed way. We have used the waterfall model successfully many times in during the last 30 years.
The core of the V-Model: Every development phase is facing a dedicated test or quality measures. Especially projects in the public sector often require this model. We have already executed several projects accordings to the V-Model and collected extensive experience with this approach.
CRISP – Cross-industry standard process for data mining
For some of our services there are specific processes - e.g. for the area of data analytics and data mining. Here we use the CRISP-Approach and combine it with further agile elements. The model is based on six phases, however they don´t have to be executed strictly in sequence. Often you jump between different phase, depending on the needs.
Methodology. The right approach for your project
Methodologies are tools for us which we use with purpose - not for their own sake. Important is that they improve your project. Therefore we closely align which methodologies we use ore even combine. One of our main principles is a eary proof of concept, e.g. in form of a mock up or a prototype that you can see the basic features. With that you not only have a basis for decisions but it is also easier to give feedback.
Especially for innovative topic we often use the Desgin-Thinking approach. It helps us to identify solutions wich are convincing from a user perspectiv. The central point is the customer and his needs. To better understand the problem we describe realistic users in detail (Persona). Based on this we analyse the requirements based on each user group and quickly sketch a first solution to develop a prototype - which we test based on the target group. The main principle: a iteration of testing, feedback, optimizing and re-testing with man agile aspects.
Rapid prototyping is based on definied requirements however it involves the user stronger in the development process. Especially with complex or very innovative systems we like to use this model - as it is often is difficult do explain the requirements. A prototype in a early development stage helps you to test early and give feedback during the development. Hereby we avoid developing a application based on unclear requirements which doesn´t fit to your needs and must be adjusted with high efforts after development. Rapid prototyping can be combined with agile development processes easily.
Lean Start Up
The lean start up concept we use if we want to bring a suitable solution into the market very fast. The main principle: fast, repeating development iterations; we develop a first product very early (build), collect feedback from users (measure) and optimize based on that (learn).
To speed up the process we use a Minimum Viable Product (MVP). We don´t start the development with a completly specified target application but rather with the questions: What are the minimum features needed that the application usable. To be able to use the application as early as possible we only implement the minimum requirements and then extend it coninously. Only what is really required will be implemented. Hereby we can avoid to implement costly but unnecessary features which will not be used later on.
For a optimal result we also use A/B-Tests. This means: We develop two different versions of the same feature. Some users will use version A and the other users use version B. The feedback decides which version will be implemented.