Classic waterfall or agile?

Often it is not a question of either-or, but a compromise of or a combined use of both. To establish requirements, it is advisable to start classically in order to set the course for software development. The implementation can then be agile in order to be able to react more flexibly to changes in the requirements.

Automated provision of development environments:

We rely on container-based development environments to quickly set up a runnable development environment for new project members.

Automated build pipelines:

We use continuous delivery pipelines for automated build processes, static code analysis, automated testing, and deployment of test and integration environments. This keeps code quality high and minimizes the probability of errors in recurring processes.

DevOps:

In modern software development, especially in agile process models, development and operation must be kept as close together as possible. We ensure this by applying the DevOps approach.