Get in touch
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.
Agility & Organisation
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
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: