serverless computing

Agile Culture – Change

The first part of this article series dealt with the fundamental question of what culture is, how culture can be understood, and what impact culture has on the way we work in an organization. After this stocktaking, the second part deals with the question of how culture can be actively developed.

Agile Culture – Introduction

Agility has long been a topic in organizations of all sizes. In an environment of increasing complexity, agility can become a key competitive advantage. It's no wonder, then, that companies want to use agile frameworks to organize knowledge work. However, introducing techniques is not enough. Becoming truly agile as an organization requires nothing less than a cultural shift. This understanding is equally important for management and team members, as development teams are often agile islands in a non-agile organization that limits their potential.

Kanban primarily focuses on flow

Kanban is an agile alternative that’s been receiving more and more attention in software development lately. Praised for its flexibility and simplicity, this method is known for the fact that instead of focusing on maximum utilization, it optimizes flow—the flow of work. We spoke with Agile coach Thomas Schissler about Kanban’s possibilities and its challenges.

Prerequisites for Continuous Deployment in enterprises

Companies often have an extensive application landscape. Nevertheless, there’s often a desire or need to regularly put new versions of the products into production, either to deliver new features or to close security gaps. This article presents prerequisites for continuous deployment using a roadmap. We will address the challenges of availability, security, and quality requirements. Special attention will be paid to the aspect of distributed responsibilities, independent of a successful establishment of DevOps culture.

ScrumBut – is it the solution?

When talking about successfully implementing software projects, Scrum as a framework paired with agile development is the current state of the art. You almost feel transported back to your teenage years, listening to schoolyard conversations about “the first time”. The comparison with agile development using Scrum isn’t so far-fetched. Everyone wants to do it, everyone says they do it, everyone seems to do it better than you - and yet, probably only 10 percent do it. And those who really do it, do they do it “right”?

Agile estimation and planning

In the previous article "Scrum - an introduction for developers", we briefly addressed the topics of product backlog and user stories. We explained that an assessment of requirements with regard to scope and complexity is also necessary for agile product development. This article will go into this in more detail. We will provide an overview of how to move from time estimates and a content framework for a rough roadmap, or release planning to a concrete estimate of requirements for planning the iteration. It will become clear that developers help to get the estimates underway, especially during the process of estimating as a basis for planning.

Stay tuned:

Behind the Tracks


Kubernetes Ecosystem

Docker, Kubernetes & Co

Microservices & Software Architecture

Maximize development productivity

Continuous Delivery & Automation

Build, test and deploy agile

Cloud Platforms & Serverless

Cloud-based & native apps

Monitoring, Traceability & Diagnostics

Handle the complexity of microservices applications


DevSecOps for safer applications

Business & Company Culture

Radically optimize IT

Organizational Change

Overcome obstacles on the road to DevOps

Live Demo #slideless

Showing how technology really works