Privacy and Cookies

For full functionality, this website places cookies on your computer. In addition, cookies are placed for tracking visitor behavior within Google Analytics. This information helps us improve our website. The cookies contain anonymous information and remain in your browser for a maximum of 2 years. Read more

Agile management: get rid of release thinking!

A continuous go-live of an application. Preferably five times a day. Madness? Certainly not. The entire lifecycle of an application is one process. Agile management provides feedback on the development of an application.



Fixing a bug sometimes only takes two hours of programming. How can the release containing the fix take weeks – or months – to arrive? That's all in the organization of traditional management: strictly separated roles of operations and developers. And we have to get rid of that.

Instead of releases, we should strive for a continuous go-live of an application. That means further development every day. Building improvements every day. And customers who can ask questions as often as they want. We call that Agile management. Madness? No. Management is feedback for the construction of an application. You think about management from the start of development. That is why we must eliminate the walls between design, development and management. The entire lifecycle is one process!

Breaking down walls

An integrated process starts with a multidisciplinary team of professionals. A team in which everyone is aware of the development, testing, rollout, use and maintenance of an application. Knowledge sharing is essential. In the traditional approach, the roles of developers and operations are strictly separated. Is there a bug in the software? Then, the discussion immediately arises as to which release the fix should be included in. And that can take a long time. With Agile management, this is a thing of the past.

Improvements vs. disruptions.

Continuous updates are possible through automatic testing and the automatic rollout of an application. Users are not bothered by this. Moreover, the user experience can always be optimized based on user data. Change and improvement of the application are therefore paramount. Unlike traditional management, Agile management is less focused on disruption, for example, due to bugs. However, because an application is continuously updated, an adjustment can be made in no time in the event of a disruption.

The rollout of an application is often seen as 'difficult'. But difficult becomes easy as soon as you break down the walls between development and operations.

- Goran Balaban, director

The right tools.

Collaborating and automating testing and rollout is not possible without the right tools. Fortunately, Application Lifecycle Management (ALM) tools make everything possible. So real-time collaboration between administrators and developers, project monitoring and reporting, automatic testing, rollout and management. With ALM, you ensure that every team member knows who changed what, when and why in the development process. This means there are never any last-minute surprises, and continuous delivery always continues.

A grip on IT management

No more time-consuming transfers from developers to operations. No more periodic releases in which the correct fixes have been made on paper. And no patches to 'fix' problems. We must strive for continuous delivery as much as possible. You reap the benefits of this already during the development phase. It shortens the time-to-market and increases control over an application.

Please contact us for more information.