Agile Methods:
7 Basic Principles
for Integration Projects

We like to start small: A microservice with the ideal technology for your first application. In the further course of the project, the architecture will be extended by more and more microservices with a linear constant effort. For example, our customers now use more than 200 microservices productively. Meanwhile we rather advise against central ESB products, because they have a very high initial effort. From a certain range of functions onwards, they can only be further expanded with exponentially increasing effort.

We live by the "API first" paradigm. In order to be able to develop as independently and efficiently as possible later on, we always focus on a consistent, coherent and lean API design at the beginning. We describe SOAP and REST interfaces according to WSDL and OpenAPI standards. All connected partner systems can rely on our API design, and we are happy to provide simulators at an early stage. And our team can focus on the actual implementation of source and test code using code generators. Using this approach, our integration experts have designed countless interfaces and connected just as many software systems for productive message exchange. You can read more about this here.

We are the inventors of the open source frameworks Citrus, which was developed especially for integration needs. It offers much more possibilities than other tools like SoapUI, Wiremock or Testcontainers. In addition to our productive source code, our team also provides the corresponding Citrus test code for all specified positive and negative use cases (such as timeouts, SoapFaults and many more). In our projects, the customer's QA department usually no longer tests itself, but only checks our test protocols.

The mindset is crucial: we have internalized the 12 Agile Principles. Depending on the project requirements, we use Scrum or Kanban as the process model. Without exception, we have integration experts in our team who work completely self-organized. Requirement analyses before the implementation of a task and code reviews afterwards are an absolute matter of course for us, as are regular code refactorings. At regular intervals we look back in retrospect and try to improve further. Of course, all integration experts regularly attend further training courses on current IT trends.

Microservice and cloud-native architectures mean that software engineers no longer just "code", but automatically perform operational tasks as well. Here, too, we make sure that the operating effort remains as low as possible, not only for installations, but also, for example, through simple monitoring health checks, easy access to log files and much more.

Depending on the container platform, we use the available options for continuous integration to continuous deployment. For many customers we are now technically capable of deploying several times a day in production. Many productive deployments are completed in a few minutes without downtime.

This enables us to form powerful teams in which all DevOps competences are bundled.

We know what we are doing and we prefer to do it self-determined. With our Agile Fixed Price we have created the possibility to work as efficiently as possible in close coordination between the customer and our team, while at the same time you as our client can be absolutely sure of your budget.