Blog

DevOps Conference
The Conference for Continuous Delivery, Microservices,
Containers, Clouds & Lean Business

Domain Driven DevOps Demystified

DevOps was set in motion in 2008 with the encounter of two people at an Agile conference in Toronto: Andrew Clay Shafer and Patrick Debois came together in a meetup on the topic of "Agile Infrastructure". Later, the term DevOps was coined for the better collaboration between developers and operations teams.

Progressing Continuous Delivery

Progressive delivery decouples code deployment and feature release. This is enabled through well-proven techniques to provide product owners, delivery, and system reliability engineering (SRE) teams with significantly more control and flexibility in their value streams. High-performing delivery teams are driven by curiosity and this means ongoing customer experimentation. But how do we achieve this at pace and without destabilizing our systems?

Dev(Ops) Experience Cloud-Native

The growing market share of cloud systems clearly shows that an increasing number of software systems are being operated in the cloud. As a prerequisite, more and more developments are cloud-native. The term Dev(Ops) Experience Cloud-Native refers to "development for the cloud" and "deployment in the cloud." Sometimes it's difficult to tell whether something is more Dev or more Ops, which is why we talk about the Dev(Ops) Experience.

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.

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

Security

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