Services & Competences

Consulting & Enablement

Co-Creation & Acceleration

Development & Technology

Academy at the glance

Agile competencies

Agile competencies at the glance

Quality as a team approach

Exploring Requirements

Software testing & test automation

Software testing & test automation at the glance

Exploratory Testing – Deep Dive

Frontend & Backend for Testers

Test automation - Selenide

Test automation - Selenium

Test automation - Cypress

Test automation - Appium

Cloud & DevOps at the glance

Terraform in action

DevOps Training “From Zero to Cloud”

Cybersecurity & access management

Cybersecurity & access management at the glance

OWASP Top 10 & Training Lab

Software development & architecture

Software development & architecture at the glance

Strategic Software Architecture

Tactical Software Architecture

Introduction to advanced Go patterns

First steps with Flamingo

Industries Overview

Telco at the glance

Telco Trendbook

Fiber expansion

Healthcare at the glance

Digital Experience Management for Healthcare

Digital Experience Management for Healthcare at the glance

Bare.ID for Healthcare

Digital catering management

All AOE Products

Company Overview

Our values & culture

CSR & Sustainability

Insights Overview

Blog at the glance

Project managers and product owners: kind of the same thing, right?

Explaining the roles in agile software development – Backend Developer

Explaining the roles in agile software development – Frontend Developer

Launch AOE Careers: Beyond a typical career page

The future of content management

Explaining the roles in agile software development – Scrum Master

Explaining the roles in agile software development – Product Owner

Generative KI and Large Language Models (LLMs) – A Glimpse into the Future

AOE Technology Radar #7

Most family-friendly employer 2023

AOE in the intrinsify podcast

Cloudland talk: Container Vulnerability Management in Kubernetes

11 tips for a successful cloud migration

Zero Trust - the hard way

AOE Behind the Screens: Backend Developer Fabian

Future-proof IT security concept: What companies should know

AOE Technology Radar #6: What's new?

AOE Behind the Screens: Frontend Developer Klara

Cybersecurity trends: What's important in 2023?

Entscheiderfabrik: AOE, PLANFOX & PlanOrg with „Rethinking the digital patient journey“

DKMS registration: Why we participate

Events at the glance

TechTalk Wiesbaden #3

BarCamp RheinMain

TechTalk Wiesbaden

Marketing Club Mainz Wiesbaden at AOE

SEIBERT MEDIA OpenSpace with Friends

Sustainable Future .digital

Bare.ID: CSK Summit 2023

Usability Testessen

CSR Regio.Net Networking Workshop

TechTalk Wiesbaden

Get in touch

We use HubSpot CRM to process and manage contact and information requests. Please accept the "Functional Cookies" and reload the page to load the contact form.

Thomas Layh

Development

Thomas Layh has been an avid TYPO3 fan for more than 7 years. For more than 5 years he has been developing state-of-the-art Open Source solutions using TYPO3, TYPO3 Flow and Symfony2. His blog deals with various topics such as web development and mobile development with Android.

http://www.layh.com/

Agility & Organisation

Systemic Consensus Principle

Mid-May I was at the Scrum master gathering hosted by our colleagues at Seibert Media. The meeting, as always, was a successful event; Scrum masters from different companies met to discuss a wide variety of topics from the agile world. In one of the sesions Joachim Seibert introduced a method for making decisions that heretofore was unknown to me. I found the technique, in which decisions are arrived at in a team, to be extremely interesting. The methodology, which he described using an example, is called the “Systemic Consensus Principle.” Up until now I had been waiting for an opportunity to use this approach for decision-making in my team – just to see if it actually works. After having used the method recently I am able to state that it works really well. And the feedback in the team was also positive. However, this approach is not applicable to all decisions; there are decisions for which the method is not 100-percent appropriate. The principle is based not on voting for something but saying how strongly you reject any given option. In this way one attemps to find that option that the participants are best able to live with. The method is explained comprehensively on the following pages; therefore, I will forego explaining it myself: Systemic Consensus PrincipleThe Method Happy decision-making!

AOE press releases

Daily stand-up with thirteen people

Thomas Layh describes one possible solution to a basic Scrum problem: How can the daily stand-up meeting be limited to just 15 minutes in large teams? The Agile Alliance Guide lists the three questions used to structure daily stand-up meetings as: