Hello, I'm Thierry de Pauw
Continuous Delivery Coach - Software Engineer
Hire me!

About me

Lean/XP Full-Stack Software Engineer with a DevOps mindset. I do backend development and frontend development. I set up development infrastructures, define software and enterprise architectures, have lots of interest in operations and coach teams in adopting eXtreme Programming principles.

Along the years I have been a bit everything: Software Engineer, (Architect), Technical Team Leader, Scrum Master, Product Owner and Agile Technical Coach.

I like to help teams in creating meaningful software, with a keen eye for code quality and software delivery process - from customer interaction to continuous delivery. Instead of balancing quality & delivery, I believe and practice that better quality is actually a way to more and better deliveries. To me feature delivery and code quality goes hand in hand.


Software engineering

My primary role is "Software Engineer". I code and I am passionate about it. This is my bread and butter. But I am not a Monkey Coder. I do the whole shebang from inception over coding, testing to releasing into production and monitoring the damned application.

I pay a lot of attention to quality of code and maintainability.

Without these skills, I cannot be a proper Agile Technical Coach and I cannot help organisations achieve a state of Continuous Delivery. Everything I know, I learned through delivering working software in production.

Agile Technical Coaching

Based on the 15+ years of experience delivering software projects I can help teams in adopting eXtreme Programming skills like Test Driven Development, Refactoring, Pair Programming, Test Automation, Simple Design, Collective Ownership, Continuous Integration.

Continuous Delivery

I help organisations and teams achieve a state of continuous delivery, i.e. being able to release product increments sufficiently reliably and quickly to satisfy customer demand.

It is first and foremost a set of principles and practices to adopt. These will help teams deliver significantly faster at a sustainable pace, with higher quality and lower costs. This involves both technological and organisational changes.

Continuous Delivery is not a tooling problem. The tooling is the easy part to solve.


From twice a year to twice a month: the story of No More Majors

The Belgian Federal Pension Service (SFPD) has a large IT department with more than a dozen teams working on the same application. Over the course of a few years, these teams developed an agile way of working at the team level but were struggling to work effectively on a larger scale.

Continuous Delivery in 4 months for 15 teams and their 1 monolith

15 teams, 1 shared monolith, 1 release every 6 months, and product demand for 1 release every 2 weeks. How do you know where to start with Continuous Delivery, when you’re surrounded by technology and organisational challenges?

Feature Branching considered Evil

Feature branching is again gaining in popularity due to the rise of distributed version control systems. Although branch creation has become very easy, it comes with a certain cost. Long living branches break the flow of the software delivery process, impacting throughput and stability.

Continuous Delivery is more than just Tooling, It's a Mindset

So your organisation wants to implement Continuous Delivery. But is your organisation ready for this ? Does it have the right mindset ? To be successful with Continuous Delivery, you have to adopt the proper mindset as a whole organisation. Just throwing tools at it will not do the job.

3M EUR later: Moving a team to become Agile in a Company with Too Much Money

How do you go from a ragtag of people having no idea what it means to be Agile, stuck in eternal maintenance and operational work, applying none of the basic software engineering practices to a team of DevOps delivering value for their customers in sprints of 2 weeks ?

Facts and Fallacies of Continuous Delivery

Continuous Delivery brings a lot of value to your organisation. It will allow you to reduce your time to market for new features and bug fixes. It is a significant predictor of company performance.


Belgian Gambling Commission Elia Johnson & Johnson Thomson Reuters BPost KBC Inventive Designers SWIFT Bru Textiles BNP Paribas Fortis ACA-IT Solutions Barco BlueSquare World Health Organisation La Chambre - De Kamer SFPD - Belgian Federal Pension Service La Croix Rouge de Belgique PaxFamilia


Speaking at EuroSTAR Conference 2020

This week I will be speaking at EuroSTAR Conference 2020.

Continuous Integration is Not a Tooling Problem

There is this commonly accepted, hard-grained belief in the software industry. By dropping a build server in a team, they get Continuous Integration magically for free. This belief is further incentivised by the marketing of build server vendors.

Interview with Thierry de Pauw — about his journey with Continuous Delivery

In this post, Leena interviews Thierry de Pauw, a Software Engineer who coaches on Continuous Delivery and other Software Engineering Practices. His focus is helping teams to improve the flow of software delivery.


Measuring Continuous Delivery by Steve Smith

This is a full write out, almost word for word, of Steve Smith’s presentation ‘Measuring Continuous Delivery’ at Pipeline Conf 2017. I’ve written down this presentation, together with the first version of this presentation at the LondonCD meetup, to be better prepared to review Steve’s book Measuring Continuous Delivery. – Thierry

Contact me

Thierry de Pauw

Continuous Delivery Coach - Software Engineer

Business details


Eendrachtstraat 101
9000 Gent, Belgium
VAT BE0889.731.807

It doesn't matter what you improve, as long as you're improving something.
Make experiments.
Fail Fast.