Power Platform Solution Architecture: ALM

In this post, we’ll begin to look at the element of this category around solution architecture for the Power Platform that is application lifecycle management or ALM. We’ll look at what ALM is in the context of the Power Platform, and the responsibility of… READ MORE [https://lewisdoes.dev/blog/
black fixed gear bike beside wall
Photo by Pixabay on Pexels.com
In: Low Code Lewis Content 🚀

In this post, we’ll begin to look at the element of this category around solution architecture for the Power Platform that is application lifecycle management or ALM. We’ll look at what ALM is in the context of the Power Platform, and the responsibility of a solution architect when it comes to this process for implementations and engagements.

What is application lifecycle management?

Let’s first start talking about application lifecycle friends. This is effectively the cycle and process a software solution goes through from planning, all the way through to monitoring, support and continuous iterative development. Application lifecycle management is the process which supports this wider cyclical movement, and usually refers to the technical element of moving digital solutions between different stages in the process.

How does it work on the Power Platform?

So when it comes to the Power Platform, as you’re probably familiar, we have the capability of solutions which we use to package apps and customisation objects which we can then export from one environment to import from another.

Then using this same mechanism we can use either out-the-box or outer platform tools such as Azure DevOps to start to automate and extend this process to meet our CICD requirements, integrating with source control tools, repositories and more.

Where does the solution architect come in?

So in this process, where do we come in as a solution architect? So friends… for this responsibilities will look a little along these lines…

A solution architect should lead and own the creation and planning of the ALM strategy for the engagement. They should determine the appropriate strategy based on the size and elements of the project (for example fully automated DevOps pipelines and source control use wouldn’t necessarily be needed for a small or even medium t-shirt sized solution). Finally they should work with various other team members to support their tasks in following the ALM strategy and plan.

What’s coming up?

So friends, stay tuned as we’ll be continuing to talk about ALM for solution architecture on the Power Platform in upcoming posts! 📧

Written by
Lewis Baybutt
Microsoft Business Applications MVP • Power Platform Consultant • Blogger • Community Contributor • #CommunityRocks • #SharingIsCaring
Great! You’ve successfully signed up.
Welcome back! You've successfully signed in.
You've successfully subscribed to LewisDoesDev.
Your link has expired.
Success! Check your email for magic link to sign-in.
Success! Your billing info has been updated.
Your billing was not updated.