Agility

Agile working style

For software development, we rely on the agile Scrum framework.

To us, Scrum is a reflection of healthy human common sense based on the realisation that development projects are often too complex to be planned completely from the beginning and based on experience which has shown over the course of development that many changes are either required or simply make sense.

With planning and implementation cycles with a rhythm of 2 to no more than 4 weeks and regular feedback meetings, Scrum ensures that manageable functions are developed and that responses to changing requirements can occur quickly. In each cycle (called a "sprint" in Scrum), executable software which expands the previous version to include directly usable functions is created. This creates transparency and security over the course of development and a solid basis for subsequent planning steps.

Planning and implementation cycles

For many years, agility has been a proven way to operate – its advantages are simply compelling. Self-organised teams and good internal and external communication increase our customers' development progress, shorten their delivery intervals and increase flexibility and creativity over the course of development. The result: top quality!

For many years, agility has been a proven way to operate

For the period of a development cycle, the development team focus solely on the work planned – they don't switch back and forth between different tasks and projects. New tasks and requirements are collected in a product backlog, prioritised and taken into account when planning the next sprint. Efficiency in development and high quality software are the result.

For the period of a development cycle, the development team focus solely on the work planned

Naturally, there are also situations in which new tasks arise on a daily basis and a direct response to requirements is essential. This applies for products with support requests, for the IT department, sales and, last but not least, for the administration. Kanban, a working style of the Toyota production system, has proven its value to us here. Just like in Scrum, tasks are collected in a backlog, but re-prioritised and continually revised on a daily basis.

Naturally, there are also situations in which new tasks arise on a daily basis