You don’t control the truth in Production!

by Jun 13, 2024

You don’t control the truth in Production!

Now a days multiple teams/projects are working on the same Dataverse production environment.

So thinking you can manage the complete production truth in your ALM pipeline is strange.

Not every environment is 💯 equal to production. Accept this and things will be easier.

Don’t treat production as an environment where your team controls the full truth, but as an environment that can be changed by other people or parties.

When you change this mindset, some things in ALM don’t fit anymore.

When you accept change from outside, you will change your deployment. It will make your ALM simpler.

Example: Why move third-party solutions through your pipeline? Just install it manually.

When your ALM doesn’t need to account for everything, it will be simpler.

When ALM is simpler, every team member can maintain it.

Do you think you control the truth in Production?

#
Remy van Duijkeren

Remy van Duijkeren

Power Platform Advisor

Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.

Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).

Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.

Services:
– Strategy and tactics advise
– Automating and integrating

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

Backlog: The Black Hole of ideas

Backlog: The Black Hole of ideas Is your backlog turning into an ever-expanding universe of forgotten dreams? We all know that mix—a jumble of big ideas and tiny tasks waiting for their day in the sun. Some items linger for years. Why do backlogs grow? Because we...

read more

The Trade-off Between Budgets and Quality ⚖️

The Trade-off Between Budgets and Quality ⚖️ In my previous post, I talked about shifting from Estimates to Budgets for feature development 💡. Let's dive deeper. Using a Budget instead of an Estimate introduces a trade-off: Scope and Quality adjust to fit the time...

read more

Budgets instead of Estimates

Budgets instead of Estimates Estimating a feature is difficult and is often a guess (or even a lie). An Estimate is for a fixed scope. So, you need to think deeply how to implement the feature, before giving an Estimate. The business can then use the Estimate to...

read more