Christiaan Verwijs

Scrum Master, Trainer, Developer & founder of Agilistic

If you're a Scrum Master, Change Agent, Agile Coach or otherwise interested in involving and tapping into the wisdom of everyone, Liberating Structures are a wonderful extension of your toolkit. In this post I explain why and offer some concrete examples. If you'd like to experience Liberating Structures first-hand, Johannes Schartau and I gladly invite you to join our workshop at Scrum Day Europe 2017. The way we communicate in groups is broken Ever been part of a status meeting where most people are checking their phones or staring into the distance? Ever been part of a brainstorm where only…

More often than not, Scrum seems like a Bad idea. At least, judging from the reasons that are often presented to me when I am asked to help a company get started with Scrum: "We want the team to take more ownership of what they're developing". "We want teams to behave more professionally". "We want to use Scrum to improve upfront estimates and stay within budget". "We want the team to work more efficiently and become more productive". "We don't have room for a project manager, so Scrum is our best option". There is nothing wrong with these goals. I'm…

If you are working with Scrum and you have a DTAP-pipeline or DTAP-street (Development > Testing > Acceptance > Production), it is my humble opinion 'that you are doing it wrong'. I strongly believe that DTAP - or at least having separate environments for testing (T an A) - is an anti-pattern in an Agile environment. In this post I explain why and what you can do about it. Recognize this? ... I don't say this lightly. I've just seen and been in too many Scrum Teams that struggle with their DTAP-pipeline. This struggle manifests in several behaviors: 'Deploy Friday': When deployment takes considerable…

Software (& product) development is never a simple endeavor. Save perhaps for projects that run a couple of days and involve only a handful of people. The vast majority of projects can easily be considered complex. By 'complex' I mean: too many variables and potential (emergent) interactions to reliably predict the (near) future. Yet, we seem to suffer from a powerful cognitive bias that makes us discount complexity with statements like 'it can't be that hard', 'we've done this before' and 'we already know pretty well what to make'. I often run into people that feel that their 'project isn't…

Automating manual work, such as deploying your application or running tests, can be a daunting task. Most teams agree that automation is important. But not knowing where to start with this 'huge and important thing', they keep pushing it into the future. In this post I offer a practical approach to get started with automation tomorrow. Automation is one of the cornerstones of Agile software development. The idea is that manual work is tedious, error-prone and therefore something you're likely to do as infrequently as possible. This includes tasks such as testing your application and releasing a new version of…