I like to take Continuous Delivery to the extreme!

by May 1, 2023

I like to take Continuous Delivery to the extreme!

I was always feeling friction doing ALM. Following the so-called best practices of others.

Practices which are often based on not trusting each other. Adding more environments as stages, adding approval steps, doing pull request, branching.

People like David Farley give me insight into where the friction came from. Causing longer feedback cycles. Longer time to deliver.

How extreme am I?

❌ No branching

✅ Commit to master (main)

❌ No Pull Requests

✅ Deploy on every commit

❌ Limit stages (environments) to Production

✅ Acceptance testing in Production

❌ No rollback of deployment (instead fix it with a new deployment)

✅ If tests are successful, auto deploy to Production

Or is this too extreme?


Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

Improving Optimization?

Improving Optimization? The traditional steps of Optimization: 1. Eliminate 2. Automate or 3. Delegate What if we added a missing element? Simplify. Before automating a convoluted workflow or delegating a tangled task, strip away the unnecessary. Make processes leaner...

read more

Unit tests for Dataverse plugins?

Unit tests for Dataverse plugins? I must admit, I almost never write unit tests for Dataverse plugins. Plugins are often quite simple, testing them in isolation is not particularly useful. Often you only test a couple of if-statements. Unit tests don't bring a lot of...

read more

New Dynamics 365 browser extension

New Dynamics 365 browser extension I'm trying out the new -Power Roles- extension and it looks very promising. You browse to a Dynamics 365 (or Power Apps) app and then you press -record-. It will then monitor all the action you do in the app and propose which...

read more