Power Platform Solution Architecture: Considerations for post go-live

In this next post within my series on Power Platform solution architecture we’ll look at the considerations we need to start to make for things that should happen for ongoing operations that continue to work following go-live and the beginning of use of a… READ MORE [https://lewisdoes.dev/blog/p
unrecognizable woman demonstrating light bulb in hands
Photo by Anete Lusina on Pexels.com
In: Low Code Lewis Content 🚀

In this next post within my series on Power Platform solution architecture we’ll look at the considerations we need to start to make for things that should happen for ongoing operations that continue to work following go-live and the beginning of use of a solution.

Recap

Support & Continuous development

So with any solution we implement, especially those greater in size and including a medium t-shirt size we’ll most likely want to have a dedicated team support and continue to improve this solution.

But what do I mean by this? Let’s explore this a little more…

Support

For solutions, there are always bound to be some form of issues that come up along the way through use, especially if planned for utilisation changes. Say for example, the number of users on the platform and that use the solution dramatically increases, or the number of customer requests dramatically increases due to our organisation size and customer base size.

All of these kind of things, can cause issues to arise such as the hitting of platform limits which cause degradations and more. There are also from time to time some bugs which can make their way past go-live without being noticed.

For these kind of things it’s important we have a support function in place to be able to handle them and resolve issues, or consult the appropriate stakeholders if development or broader work is required.

Continual improvement

There is also an element to which business requirements will constantly change and organisations will constantly be looking to improve their workings.

For these kind of cases where potential improvement may need to be made to a solution with small items being prioritised that are perhaps less regular and don’t require huge design or scoping efforts, we can implement a smaller sized regular development team who pick up these types of requests and work to a periodic based deployment schedule.

It’s important to consider whether this kind of function might be necessary based on the size of the solution being implemented.

It should also be maintained that any overly large requirements or collections of requirements perhaps might not fit into this type of function and may require a subsequent project to the initial implementation. This should be reviewed by the same or another solution architect.

What’s coming up?

So in the next couple of posts friends, we’ll look at some of these points in more detail including topics such as handover, support and continual improvement. 🚀

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.