In previous blog posts (see below), we provided the essential facts about agile software development. Agility can help us solve complex problems, especially when operationalisation is not done in a dogmatic way. Today, we will be looking at the interplay between agility and ambidexterity.

In previous blog posts in this series, we found out about agility in software development. Empirical knowledge also plays a key role here, too. I will explain why in my blog post.

In my last blog post, I introduced you to six of the twelve agile principles. These should help us not only to implement agility, but to live it, too. In this blog post, I’ll introduce you to the remaining six principles in more detail.

It’s important to live the Agile Manifesto. Twelve principles, which can be understood as codes of behaviour or rules of the game, were established for this very purpose. In this blog post, I’ll introduce you to the first six principles in more detail.

In my first blog post, I primarily focused on the historical background of agility in software development and explained what the term means in basic terms.

I would like to dedicate a series of blogs on agility to the term ‘agility’ itself. This will cover topics such as agile software development, agile frameworks, agile mindsets and agile methods. My goal is that everyone – from the classic waterfall manager to the full-blooded agilist – will find something to take away. The first part is all about the question of whether we really work in an agile way.

Low-code development platforms are becoming increasingly popular with companies because they enable them to create applications independently, even if they have little or no programming knowledge. In my blog post, I’ll describe the origins of low-code, explain how it works and list important considerations for its implementation.

My goal in software development is to build programmes and features that people need and like to use. Only on the way did I slowly realise that simply writing code would probably not be enough. This journey continues to this day. In my blog post, I would like to share the crucial insights and changes of mind I had and give you an idea of what the world of software development is like.

Applications often contain resources that should only be available to certain users. Management users, for example, administer the information of their employees, whereas sales users administer the information of their customers. This requires closed areas, access to which is controlled by permissions. In this blog post, I would like to show you how to manage these access permissions in Keycloak and how to assign them to groups of users.