Skip to main content

Release trains are NOT the solution

One of the techniques that you see in bigger organizations that struggle to move to an Agile mindset, is the introduction of Release trains:

A release train tries to align the vision, planning, and interdependencies of many teams by providing cross-team synchronization based on a common cadence. A release train focuses on fast, flexible flow at the level of a larger product.

It is especially used in SAFe(Scaled Agile Framework) organizations. Their definition of a release train is:

Agile Release Trains align teams to a shared business and technology mission. Each is a virtual organization (typically 50 – 125 people) that plans, commits, develops, and deploys together. ARTs are organized around the Enterprise’s significant Value Streams and exist solely to realize the promise of that value by building Solutions that deliver benefit to the end-user.

Based on the definitions above you would think that a release train is something you should aim for, an end goal you should achieve to become ‘Agile’. I don’t agree with that. Although release train can help you get in the right direction, they are a temporary workaround for an organization moving to continuous delivery. THAT is what you should aim for. Release trains are a remedial technique to get out of the mess that the release process in most organizations is today.

The biggest risk is that release trains bring you on the path of distributed monoliths. As you get used to the fact that all your services are deployed together, your architecture will start to depend on it. Now you have all the complexity of a distributed system, but also the downsides of a single unit of deployment as well.

Every part of your architecture should be independently deployable.

Intrigued? Read following article: https://rollout.io/blog/release-train-crashed/

I’ll leave you with one quote:

“If you have a release engineer/manager chances are you have a distributed monolith”

Popular posts from this blog

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.